Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2022-06-21
16:08:12 gibi #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 12 new untriaged bugs (-2 since the last meeting)
16:08:13 elodilles i mean, does it make any difference to pin libvirt compared to keep the job non-voting ?
16:08:33 artom Looks like a libvirt fix is being released, based on https://bugzilla.redhat.com/show_bug.cgi?id=2092856
16:08:39 gibi elodilles: if we keep non-voting and the libvirt issue is fixed the job will start being green again
16:08:47 artom So maybe just wait for that to land in CS9, and make the job voting again?
16:08:56 gibi artom: yepp, we can do that
16:09:09 Uggla o/
16:09:20 elodilles ack, then that is the best option for now
16:09:28 gibi ack, seems like we do that as that is easy
16:09:50 gibi so untriaged bug backlog looks healthy thanks melwitt for the triages
16:10:14 gibi #info If you are interested add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:10:22 gibi next the baton goes to bauzas
16:10:29 gibi I will ping him when he is back
16:10:34 gibi let's assume he took it :)
16:10:41 gibi #info Next bug baton is passed to bauzas
16:10:50 gibi any other bug you would like to discuss?
16:11:16 artom Not me? Cool then
16:11:42 gibi I think bauzas rescheduled himself as he missed having the baton during the summit
16:12:00 gibi (I'm following bauzas agend from the wiki :)
16:12:07 artom For once it's not my job to figure out the "overwatch" rotation :P
16:12:15 artom (Sorry for leaking downstream)
16:12:32 gibi anyhow I don't see any bugs raised so moving on
16:12:35 gibi #topic Gate status
16:12:40 gibi #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:12:46 gibi #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:12:57 gibi looks green
16:13:07 gibi #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
16:13:18 gibi green too
16:13:25 gibi #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:13:29 gibi #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:13:35 gibi we had two gate blockers on Friday
16:13:42 gibi the one with the libvirt issue from above
16:13:56 gibi and another with a tempest test case failure
16:14:19 gibi the tempest failure was fixed by https://review.opendev.org/c/openstack/tempest/+/846345/3
16:14:27 gibi so the gate should be OK now
16:14:36 gibi but honestly I haven't checked the results today
16:15:29 gibi I quickly checked the master gate is not blocked
16:15:42 gibi any gate issue we need to discuss here?
16:16:51 gibi #topic Release Planning
16:16:57 gibi #link https://releases.openstack.org/zed/schedule.html
16:17:02 gibi #info Zed-2 is in 3.5 weeks
16:17:07 opendevmeet Vote using '#vote OPTION'. Only your last vote counts.
16:17:07 opendevmeet Begin voting on: Spec review day on July 5th ? Valid vote options are , yes, no, .
16:17:07 gibi #startvote Spec review day on July 5th ? (yes/no)
16:17:26 gibi #vote yes
16:17:59 Uggla #vote yes
16:18:48 gibi others?
16:19:13 elodilles #vote yes
16:19:50 elodilles (though my vote really does not count i guess o:))
16:20:03 sean-k-mooney #vote yes
16:20:25 sean-k-mooney i think i can do the 5th but folks form the us may be off
16:20:44 gibi hangover from 4th of July?
16:20:53 sean-k-mooney perhaps :)
16:21:21 elodilles :)
16:21:21 sean-k-mooney i think if there are no objections however the 5th shoudl be fine
16:21:51 opendevmeet yes (4): Uggla, sean-k-mooney, gibi, elodilles
16:21:51 opendevmeet Voted on "Spec review day on July 5th ?" Results are
16:21:51 gibi #endvote
16:22:18 gibi #action bauzas to send out a note to the ML about the spec review day on 5th of July
16:22:35 gibi #topic Review priorities
16:22:42 gibi #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+label:Review-Priority%252B1
16:22:59 gibi #link https://review.opendev.org/c/openstack/project-config/+/837595 Gerrit policy for Review-prio contributors flag. New proposal there, please vote.
16:23:03 gibi #link https://docs.openstack.org/nova/latest/contributor/process.html#what-the-review-priority-label-in-gerrit-are-use-for Documentation we already have
16:23:26 gibi anything to raise about review priority?
16:24:19 gibi #topic Stable Branches
16:24:24 gibi elodilles:
16:24:26 gibi your turn
16:24:44 elodilles #info gates are mostly not blocked
16:24:56 elodilles #info stable/train is blocked - melwitt's fix: https://review.opendev.org/c/openstack/nova/+/844530/
16:25:04 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:25:13 elodilles release patches proposed (yoga, xena, wallaby): https://review.opendev.org/q/project:openstack/releases+is:open+intopic:nova
16:25:27 elodilles the release patches are on the way now
16:25:34 gibi \o/
16:25:58 elodilles (sorry i've re-used last week's lines as there are not that much news o:))
16:26:36 gibi elodilles: thanks
16:26:41 elodilles np
16:26:43 gibi anything else about stable?
16:26:51 elodilles nothing from me
16:28:03 gibi #topic Open discussion
16:28:10 gibi (artom) Can we revisit stable func test backport policy? Specific patch stack: https://review.opendev.org/c/openstack/nova/+/791480/1 Previously we didn't want to backport func test infrastructure because it just offloads the backport debt onto whoever is doing backport for older than train releases. Some time has passed now, are there still operators running < stable/train and needing backports?
16:28:16 gibi https://etherpad.opendev.org/p/r.ea2e9bd003ed5aed5e25cd8393cf9362 indicates a majority of "train or older", but how many are on the "older" half of that?
16:29:02 artom Bringing this up again because at this point there are 3 separate bugfixes depending on those test refactor patches
16:29:08 artom But basically $topic :)
16:29:28 gibi personally I'm OK to bring back any test refactors to stable branches
16:30:17 artom IIRC last time we talked about this, elodilles was worried that anyone backporting to rocky and older would get the "refactor" debt unloaded onto them
16:30:36 elodilles IF there are enough reviewers then maybe it could be OK, though it's best to keep things on the safe side and backport less risky things
16:31:11 artom Are func test refactors really risky though?
16:31:14 sean-k-mooney well test code is less risky in general since it does not affect the runing code
16:31:27 gibi it does not risk the production code, it risk the CI stability
16:31:27 elodilles artom: yepp, if we backport mass amount of functional test refactors, then it makes the backport harder for older branches
16:31:36 sean-k-mooney and in some cases are not actully installed with the production code
16:32:11 artom elodilles, yep, agreed on that. So in practice, bauzas and gibi were at summit, is anyone still doing backports for < stable/train?
16:32:34 artom As in, Red Hat will have to care about stable/train for a long time
16:32:46 sean-k-mooney :(
16:32:53 gibi I tend to propose backports to stable/pike while I were in E///
16:32:54 sean-k-mooney its true but :(
16:32:55 artom Yeah, sad face indeed
16:33:16 gibi I assume E/// still uses stable/pike
16:33:24 gibi but I don't think we will see much backports there
16:33:48 elodilles i see that there are less and less backports pushed toward old branches, though if we make it harder for developers, then it will not help the situation as well

Earlier   Later