16:00:12 <bauzas> #startmeeting nova
16:00:12 <opendevmeet> Meeting started Tue May  3 16:00:12 2022 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:12 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:13 <opendevmeet> The meeting name has been set to 'nova'
16:01:04 <gibi> o/
16:01:09 <elodilles> o/
16:01:11 <gmann> o/
16:01:22 <sean-k-mooney> o/
16:01:26 <bauzas> hello
16:01:27 <melwitt> o/
16:01:39 <bauzas> sorry I'm over the phone but let's start
16:01:48 <bauzas> #topic Bugs (stuck/critical)
16:01:52 <bauzas> #info No Critical bug
16:01:57 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 22 new untriaged bugs (-2 since the last meeting)
16:02:03 <bauzas> #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (0 since the last meeting) in Storyboard for Placement
16:02:08 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:02:19 <bauzas> artom: around ?
16:02:28 <artom> 'sup?
16:03:07 <bauzas> artom: can I pass you the next bug triage baton ?
16:03:08 <artom> I'm getting baton'ed, aren't I?
16:03:08 <melwitt> I thought we had 28 new bugs last meeting :( https://meetings.opendev.org/meetings/nova/2022/nova.2022-04-26-16.00.log.html#l-16
16:03:25 <melwitt> -2 makes it look like I didn't do anything 😂
16:03:47 <gibi> melwitt: thank you for the triage!
16:04:02 <gibi> I also remember 28 or 29 from last week
16:04:33 <melwitt> I copied gibi's doc https://etherpad.opendev.org/p/nova-bug-triage-20220426, there were a couple more where I added comments but didn't change from New bc not enough info yet afaict
16:05:00 <melwitt> (and didn't add to doc either)
16:05:07 <bauzas> yeah, thanks melwitt !
16:05:10 <artom> Should we maybe have a single etherpad?
16:05:20 <artom> So new batoners can refers to existing work/patterns/templates?
16:05:26 <bauzas> melwitt: no worries, I had some weeks the same situation
16:05:35 <Uggla> o/
16:05:48 <bauzas> I was triaged like 10 bugs but given 12 were new, I was only having a -2 value :)
16:05:58 <bauzas> or the other way, sorry :)
16:06:06 <melwitt> I think one etherpad would quickly become a megapad. but the pads are linked here so far https://etherpad.opendev.org/p/nova-bug-triage-roster
16:06:24 <artom> melwitt, aha OK that works, as long as we have a single... something
16:06:25 <bauzas> yeah, we can have a new etherpad per week, it's fine
16:06:25 <gibi> artom: I created the etherpad just to note for the meeting if there are valid but unassigned bugs
16:06:44 <bauzas> it's not actually really needed to create a etherpad
16:06:54 <gibi> not at all mandatory :)
16:06:55 <bauzas> like gibi said, he did it for him
16:07:29 <melwitt> yeah. and I liked it so I copied it
16:08:02 <gibi> (it is also good for looking back after the week and justify the time spent on launchpad :)
16:08:36 <opendevreview> Balazs Gibizer proposed openstack/nova master: Record SRIOV PF MAC in the binding profile  https://review.opendev.org/c/openstack/nova/+/829248
16:09:32 <melwitt> gibi: +1 :)
16:11:10 <gibi> bauzas: I think we can move on
16:11:18 <bauzas> ok, next topic
16:12:02 <bauzas> #topic Gate status
16:12:07 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:12:36 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:12:41 <bauzas> #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
16:12:45 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:12:50 <bauzas> #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:13:13 <gibi> melwitt: thanks for the triage on the gate bug https://bugs.launchpad.net/nova/+bug/1970642 I will try to get back to that
16:13:14 <bauzas> nothing to tell from me
16:13:30 <melwitt> this gate bug has shown back up on stable/ussuri fyi https://bugs.launchpad.net/nova/+bug/1901739 but it doesn't show up in the gate-failure tag bc it's on ussuri only
16:13:34 <melwitt> gibi: np!
16:14:27 <bauzas> cool
16:14:41 <melwitt> we're on our second recheck trying to merge  one of the gate unblocking patch on stable/ussuri https://review.opendev.org/c/openstack/nova/+/838033 :\
16:15:04 <melwitt> for bug 1901739
16:15:33 <gibi> and the original fix was to switch to zuul v3 :/
16:15:42 <elodilles> yepp, it seems ussuri is not that healthy as it should be :S
16:16:03 <elodilles> gibi: and as far as i remember we did not need that for ussuri
16:16:13 <elodilles> so this is something "new"
16:17:30 <gibi> hm we do merged the ussuri backport https://review.opendev.org/c/openstack/nova/+/795432
16:18:08 <gibi> that should have fixed 1901739 but appreantly it did not
16:19:22 <elodilles> oh. hmmm, yes, we did not backport it to *train*...
16:19:36 <elodilles> then this is definitely something "new"
16:19:37 <gibi> that is all I can add to this right now :/
16:21:15 <bauzas> could we discuss about the stable branch gate issues during the stable topic, maybe ?
16:21:32 <elodilles> ++ :)
16:21:59 <elodilles> (i planned to note this there)
16:22:32 <bauzas> ok, then next topic
16:22:37 <elodilles> (otherwise i don't have much to add for now)
16:22:41 <bauzas> #topic Release Planning
16:22:47 <bauzas> #link https://releases.openstack.org/zed/schedule.html
16:22:51 <bauzas> #info Zed-1 is due in 2 weeks
16:22:55 <bauzas> #info Spec review day planned on May 10th
16:22:59 <bauzas> ... which is next week
16:23:09 <bauzas> I've seen some new specs
16:23:14 <melwitt> sorry, I thought stable gate status was part of gate status
16:23:20 <bauzas> I'll try to review some of them tomorrow
16:23:28 <bauzas> melwitt: no worries at all
16:23:44 <bauzas> but I'd prefer to do this after all the other topics
16:23:57 <bauzas> so we'll have all the left time for it :)
16:24:28 <bauzas> anything to say about release planning ?
16:24:44 <bauzas> keep in mind to upload/update your last specs before next tuesday :)
16:26:03 <bauzas> looks not
16:26:21 <bauzas> #topic Review priorities
16:26:31 <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:26:58 <bauzas> nothing to tell here
16:30:59 <bauzas> ok, moving on then
16:31:12 <bauzas> #topic Stable Branches
16:31:19 <bauzas> elodilles: you can continue the discussion here :)
16:31:31 <elodilles> well, let's start with the basics :)
16:31:35 <elodilles> #info ussuri and older branches are blocked until 'l-c drop' patches merge - https://review.opendev.org/q/I514f6b337ffefef90a0ce9ab0b4afd083caa277e
16:31:59 <elodilles> and as we said something else problematic is there on ussuri it seems :(
16:32:06 <elodilles> #info other branches should be OK
16:32:38 <elodilles> EOM
16:32:54 <elodilles> I don't have other info for the ussuri failures for now :(
16:35:37 <bauzas> cool
16:35:42 <bauzas> melwitt: wanting to add something ?
16:36:01 <melwitt> nothing additional, thanks
16:36:04 <bauzas> cool
16:36:13 <bauzas> then we're done with this topic
16:36:26 <bauzas> #topic Open discussion
16:36:41 <bauzas> ... and we have nothing about this in the wiki
16:36:53 <bauzas> soooo, any item to raise before we end the meeting ?
16:37:13 <gibi> <crickets?
16:37:15 <gibi> >
16:38:05 <bauzas> okidoki
16:38:11 <bauzas> thanks all
16:38:13 <bauzas> #endmeeting