Earlier  
Posted Nick Remark
#openstack-nova - 2022-05-24
16:04:42 sean-k-mooney i also checked some of the incomplete form last week
16:04:46 sean-k-mooney but no change really
16:05:14 sean-k-mooney one fixed bug form stephen https://bugs.launchpad.net/nova/+bug/1974173
16:05:20 sean-k-mooney thats about it
16:06:34 bauzas ok thanks
16:06:40 bauzas and thanks again for triaging
16:06:57 bauzas elodilles: are you okay for getting the baton for this week ?
16:07:44 elodilles bauzas: yepp o7
16:07:54 bauzas thanks
16:08:00 bauzas #info Next bug baton is passed to elodilles
16:08:20 bauzas #topic Gate status
16:08:59 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:09:03 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:09:08 bauzas #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
16:09:14 bauzas as you can see ^ nothing to tell
16:09:45 bauzas both jobs and pipelines work
16:09:52 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:09:57 bauzas #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:10:05 bauzas as a reminder for everyone ^ :)
16:10:30 gibi please note that we are still playing wack-a-mole with the volume detach issue. There are still open tempest patches adding more SSHABLE waiters
16:10:49 bauzas gibi: yup, we'll discuss this for the stable topic
16:11:03 gibi ack, but this is affecting master still :)
16:11:05 sean-k-mooney bauzas: well it affects master too
16:11:10 sean-k-mooney but sure
16:11:30 bauzas yep, I know, thanks for the reminder it also impacts master
16:12:14 bauzas #topic Release Planning
16:12:19 bauzas #link https://releases.openstack.org/zed/schedule.html
16:12:22 bauzas #info Zed-1 was last week
16:12:48 bauzas thanks sean-k-mooney for accepting the rc1 releases for the projectsd
16:13:03 bauzas oh, actually elodilles
16:13:12 sean-k-mooney ya it was elodilles
16:13:25 sean-k-mooney i repled on one after the fact
16:13:27 bauzas #link https://review.opendev.org/c/openstack/releases/+/841851 novaclient release for zed-1
16:13:34 elodilles well, it had a deadline, so needed a review & merge o:)
16:13:43 sean-k-mooney we dicussed it but i forgot to do it before the deadline
16:13:51 bauzas #link https://review.opendev.org/c/openstack/releases/+/841845 os-vif release for zed-1
16:13:56 bauzas sean-k-mooney: me too
16:14:05 sean-k-mooney elodilles: strictly speaking we dont have to do it by m1
16:14:08 bauzas and i was off this friday, didn't help
16:14:17 sean-k-mooney that is just the convention the the release team are following
16:14:30 sean-k-mooney btu its not requried by the release model
16:14:34 bauzas elodilles: don't be afraid to ping me if you need me to review some release change
16:14:38 sean-k-mooney we jsut need a intermediat release :)
16:14:43 bauzas correct
16:15:06 elodilles bauzas: ack :)
16:16:36 elodilles sean-k-mooney: not necessary, yes, but if there is no -1 from the team, then release managers merges the generated patches at deadlines o:)
16:16:55 sean-k-mooney elodilles: right the deadline is actully m3
16:17:04 sean-k-mooney the docs dont mention m1 at all
16:17:21 sean-k-mooney that is jsut a hold over form the release with milestone model
16:17:31 sean-k-mooney but thanks form taking care of it in any case
16:18:48 sean-k-mooney https://github.com/openstack/releases/blob/61f891ddd7bd3b28ac7b5e7e9e1d9203fbbe297d/doc/source/reference/release_models.rst#cycle-with-intermediary=
16:19:18 elodilles sean-k-mooney: see #2, and it's last chapter: https://releases.openstack.org/reference/process.html#milestone-1
16:19:34 bauzas elodilles: how can I see whether for example os-vif is either using a cycle-with-rc model or a cycle-with-intermediary one ?
16:19:55 sean-k-mooney elodilles: yep that is not in lien with the governance doc
16:19:57 elodilles bauzas: in the yaml file under deliverables/zed
16:20:05 sean-k-mooney anyway its not importnat now
16:20:18 bauzas elodilles: ok b/c https://releases.openstack.org/teams/nova.html doesn't tell it
16:20:31 bauzas anyway, moving on
16:20:42 elodilles ++
16:20:49 bauzas #topic Review priorities
16:20:55 bauzas #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:21:00 bauzas #link https://review.opendev.org/c/openstack/project-config/+/837595 Gerrit policy for Review-prio contributors flag. Naming bikeshed in there.
16:21:06 bauzas #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:21:39 bauzas I provided a comment for https://review.opendev.org/c/openstack/project-config/+/837595
16:21:43 bauzas please review it
16:21:58 gibi done :)
16:22:38 bauzas thanks
16:22:50 bauzas at least I'm French so in general I'm not good at naming things
16:23:06 bauzas but at least I try to find a consensus
16:23:14 gibi thank you for that
16:23:39 bauzas I think all contributors know what nova-core means
16:23:52 bauzas hopefully
16:24:15 gibi that is a fair assumption
16:24:35 bauzas for other repos, we could name the label differently of course, like 'osvif-core' if this is named by gerrit
16:25:21 bauzas ie. nova-specs-core review promise
16:25:31 bauzas os-vif-core etc.
16:25:41 bauzas but this is a naming bikeshed
16:26:24 bauzas anyway, moving on
16:26:32 bauzas #topic Stable Branches
16:26:40 bauzas in general I ask elodilles
16:26:46 bauzas but this time, let me do it
16:26:52 bauzas #info ussuri and older branches are still blocked, newer branches should be OK
16:27:03 bauzas melwitt had a point
16:27:33 elodilles just an update for that ^^^ i think ussuri is blocked but the older branches are not blocked anymore
16:27:47 bauzas #link https://etherpad.opendev.org/p/nova-stable-branch-ci stable branches CI issues tracking, feel free to update with stable branch CI issues
16:27:58 bauzas elodilles: woah
16:28:11 bauzas kudos to the team then
16:28:13 elodilles bauzas: l-c branches were merged
16:28:32 elodilles bauzas: i don't say they don't have intermittent failures though o:)
16:28:43 bauzas elodilles: I thought most of the issues were related to volume detach things, which are unrelated to l-c
16:28:44 elodilles but at least they are not blocked
16:28:48 bauzas ah
16:29:23 bauzas elodilles: but then, why ussuri is blocked while older not ?
16:29:47 elodilles ussuri and train were where tempest were not pinned,
16:29:58 elodilles and where tempest is running with py36
16:30:08 elodilles if i'm not mistaken that's it
16:30:21 elodilles and gmann's train fix has landed
16:31:04 bauzas ok thanks
16:31:05 elodilles originally we thought that ussuri does not need a fix as it has zuulv3 jobs already, but that's not true unfortunately
16:31:21 bauzas gmann told me he couldn't attend this meeting, so let's discuss this again next week

Earlier   Later