Earlier  
Posted Nick Remark
#openstack-nova - 2023-09-05
16:00:08 gibi o/
16:00:11 Uggla o/
16:00:11 sean-k-mooney o/
16:00:14 elodilles o/
16:00:15 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:00:15 auniyal o/
16:00:36 dansmith o/
16:00:47 bauzas cool, people arriving fast, lovin'
16:00:50 bauzas let's start
16:00:57 bauzas #topic Bugs (stuck/critical)
16:01:02 bauzas #info No Critical bug
16:01:06 bauzas whoops
16:01:08 bauzas #info No Critical bug
16:01:14 bauzas #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 49 new untriaged bugs (+0 since the last meeting)
16:01:18 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:01:23 bauzas #info bug baton is bauzas
16:01:34 auniyal bauzas, I have few bugs to discuss
16:01:36 bauzas auniyal: any questions you have ?
16:01:40 bauzas cool, shoot
16:02:01 auniyal actully this : https://etherpad.opendev.org/p/nova-bug-triage-20230902
16:02:21 bauzas ack, looking
16:02:27 auniyal https://bugs.launchpad.net/nova/+bug/2031635:
16:02:42 auniyal ack
16:03:50 bauzas I'm not expert, I can't tell
16:04:20 auniyal I'll paste the quick ones here
16:04:29 auniyal https://bugs.launchpad.net/nova/+bug/2033393: Xena: server name is not updated in guest xml after rename ?
16:04:42 gmann o/
16:04:53 gibi so for 2031635 we need to check if https://review.opendev.org/c/openstack/nova/+/867788 is backported to stables or not
16:05:01 auniyal is it known ? does it does affect an operation
16:05:35 bauzas let's not discuss the resolution here
16:05:49 auniyal gibi, its not backported
16:06:00 gibi auniyal: then I guess we need to backport it
16:06:05 gibi as we need to support py3.8
16:06:13 auniyal ack,
16:06:16 bauzas ok, resolution set, Valid then
16:06:24 bauzas we can look at the other ones next week
16:07:01 dansmith auniyal: the instance name one is invalid, I just updated
16:07:32 auniyal ack, thanks dansmith
16:07:48 bauzas ok, let's move on then
16:08:42 bauzas #topic Gate status
16:08:47 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:08:59 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:09:04 bauzas #info nova-emulation is still b0rked
16:09:09 bauzas chateaulav: are you around ?
16:09:23 sean-k-mooney oh really
16:09:27 sean-k-mooney i was not aware of that
16:09:44 sean-k-mooney whats broken
16:10:13 sean-k-mooney test_resize_volume_backed_server_confirm
16:10:20 sean-k-mooney so that might not be related to emulation
16:10:24 sean-k-mooney the other tests passed
16:10:28 dansmith yeah not sure why that would be emulation related
16:10:31 dansmith other than that it can be slow
16:11:09 sean-k-mooney ill quickly take a look async
16:11:27 bauzas yeah probably unrelated, but alas this is the only one which fails every week
16:11:37 sean-k-mooney no obvious error in the nova log
16:11:44 gmann and a few of the fixes are merged related to this test but yes it can fail on slow maybe
16:12:50 bauzas okay, so we'll see if next round it fails again
16:13:11 bauzas any other gate information to share ?
16:14:25 dansmith otherwise I think the gate is doing better than it has in a while
16:14:37 dansmith we still need volume test attention like we have for many years
16:14:45 dansmith but life isn't as terrible as it has been
16:15:20 bauzas glad to hear such good news
16:15:45 bauzas which weren't arriving just because of luck
16:15:58 bauzas so kudos to those who worked hard on chasing
16:16:21 bauzas moving on then
16:16:23 bauzas #topic Release Planning
16:16:28 bauzas #link https://releases.openstack.org/bobcat/schedule.html
16:16:32 bauzas #info Nova deadlines are set in the above schedule
16:16:47 bauzas #link https://etherpad.opendev.org/p/nova-bobcat-blueprint-status Etherpad for tracking blueprints status
16:16:51 bauzas #info 9 blueprints were implemented this cycle, 8 got deferred (5 of them were awaiting rebases from owner)
16:17:04 bauzas thanks folks who reviewed features
16:17:23 sean-k-mooney just on last thing on nova-emulation. we didn not pin that job to < 6 concurancy so maybe we need to drop that back to 4
16:17:33 bauzas despite a very few of happy reviewers, we were able to merge a quite decent number of reviews
16:17:50 bauzas s/reviews/changes
16:17:52 gmann sean-k-mooney: but is it oom issue happening there?
16:18:08 sean-k-mooney i dont think so ill look after the meeting
16:18:26 sean-k-mooney i just assume since this is testing qemu with emulation of arm it might be slower
16:18:54 sean-k-mooney anyway we can go back to the release topic
16:19:05 gmann ack
16:19:14 bauzas sean-k-mooney: thanks
16:19:23 bauzas so, I was just saying thanks
16:20:03 bauzas we still have a couple of series that missed the target, but most of them were mostly due to merge conflicts or other states that aren't "shit, we missed to review that"
16:20:29 sean-k-mooney there was one that kind fo fell in that camp
16:20:33 bauzas we still have two long series that require proper attention next cycle if they're reproposed, as those series are very long and hard to review
16:20:36 sean-k-mooney the virtio-packed ring format
16:21:11 bauzas it was in merge conflict until last week
16:21:25 bauzas actually, until today
16:21:36 bauzas so no, it was still on the camp "the owner has to do things"
16:21:36 sean-k-mooney no it ws mergable a mount ago
16:21:43 sean-k-mooney and then went int merge conflcit in between
16:21:47 bauzas sure
16:22:10 sean-k-mooney i had tought we merged it
16:22:11 bauzas but I raised a couple of times the fact that we are requiring a correct state of a patch for being reviewed
16:22:25 sean-k-mooney it was kasyaps min version bump that caused the merge conflict
16:22:31 bauzas and it was correctly tracked in the etherpad as being 'in merge conflict'
16:22:52 bauzas sean-k-mooney: I bet no, since it was on merge conflict *before* we merged the min version bump
16:23:13 sean-k-mooney anyway im sad that missed but it is what it is
16:23:13 bauzas but I can doublecheck the timings based on the etherpad history
16:23:27 dansmith yeah I think it was in merge conflict before
16:23:40 bauzas again, that one was correctly tracked and marked as not reviewable yet

Earlier   Later