Earlier  
Posted Nick Remark
#openstack-nova - 2022-02-08
16:00:42 opendevmeet The meeting name has been set to 'nova'
16:00:42 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:42 opendevmeet Meeting started Tue Feb 8 16:00:42 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:42 bauzas #startmeeting nova
16:00:51 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:00:56 gibi o/
16:00:59 dansmith o/
16:01:02 chateaulav \o
16:01:02 gmann o/
16:01:15 bauzas sorry I was late, someone pinged me at house
16:01:23 elodilles o/
16:02:19 bauzas ok, let's start
16:02:25 bauzas #topic Bugs (stuck/critical)
16:02:30 bauzas #info One Critical bug
16:02:35 bauzas #link https://bugs.launchpad.net/nova/+bug/1959899 this is the critical bug for nova-next
16:02:45 bauzas do we want to discuss this one ?
16:03:17 gibi my last info
16:03:34 gibi that artom and sean-k-mooney figured out that this is a q35 machine type related issue
16:03:46 gibi then we turned off the test on master to unblock the gate
16:03:59 gibi I don't know if there is any fix in the works
16:04:16 bauzas oh shit
16:05:20 bauzas ok, so maybe we should put it to High ?
16:05:50 gibi yeah we can decrease it to High as the gate is not blocked now
16:05:52 gibi as we skip
16:05:56 bauzas as this test is executed in other jobs
16:06:06 sean-k-mooney we dont have a fix yet
16:06:21 sean-k-mooney artom speculated it might be related to a state tracking but with qemu
16:06:27 bauzas I'm only afraid of the fact it means we would have problems when upgrading
16:06:31 sean-k-mooney that is still pending
16:07:05 bauzas sean-k-mooney: at least this is blocking q35 to be the next machine type, right ?
16:07:13 artom The only data point I have is that it passed without q35... once
16:07:34 artom But it also passed intermittently *with* q35 on other patches
16:07:35 bauzas ah, this is different then
16:07:39 sean-k-mooney yes so q35 and pc use difffernt hotplug code paths
16:07:42 artom So... more testing needed?
16:07:50 bauzas I guess
16:07:57 bauzas anyway, let's punt the bug report to High
16:08:07 sean-k-mooney bauzas: we als think the way the device is presented in teh guest might change based on q35 or pc
16:08:09 bauzas but we need to fix this bug
16:08:21 sean-k-mooney so we shoudl keep looking into it and try and fix it
16:08:29 sean-k-mooney yep
16:08:37 sean-k-mooney it may not be fixable in nova
16:08:47 sean-k-mooney but we have nto figure that out yet
16:09:02 opendevreview Alexey Stupnikov proposed openstack/nova master: Fix clean-up process for aborted queued live migrations https://review.opendev.org/c/openstack/nova/+/828374
16:09:09 gibi artom: this test runs in tempest-integrated-compute job with pc machine type
16:09:19 gibi artom: and it appears to be green there
16:10:03 bauzas could we create another job for testing ?
16:10:18 bauzas non-voting, of course
16:10:20 sean-k-mooney this is the qemu bug we think might be relevent https://bugzilla.redhat.com/show_bug.cgi?id=2007129
16:11:17 sean-k-mooney bauzas: i htink we have enough test coverage with teh integrated job
16:11:29 gibi agree ^
16:11:31 bauzas OK
16:11:33 sean-k-mooney so i think we can move on for now and just monitor/investigate
16:11:41 bauzas cool then, we can moveo n
16:11:45 bauzas move on, even
16:11:57 bauzas #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 39 new untriaged bugs (+0 since the last meeting)
16:12:01 bauzas #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage
16:12:10 bauzas I triaged a few evident bugs
16:12:57 bauzas #link https://storyboard.openstack.org/#!/project/openstack/placement 27 open stories (+0 since the last meeting) in Storyboard for Placement
16:13:02 bauzas that's it for bugs
16:13:06 bauzas any ones to tell ?
16:14:14 bauzas looks not
16:14:20 bauzas #topic Gate status
16:14:25 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:14:34 bauzas we discussed the critical one
16:14:39 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:14:39 gibi besides the one we discussed
16:14:48 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:14:58 gibi the nova-specs doc build is broken due to sphinx 4.4.0
16:15:04 gibi fix is here https://review.opendev.org/c/openstack/nova-specs/+/828368
16:15:20 gibi and here https://github.com/sphinx-doc/sphinx/pull/10178 (thanks to stephenfin)
16:15:23 bauzas saw it, had no time to vote yet
16:15:34 bauzas vote coming up after the meeting
16:15:38 gibi cool
16:15:39 gibi thanks
16:15:59 gmann +A, 4.4.0 has caused on ext link other repo too
16:15:59 stephenfin please pile on the latter bug (+1) if you can :)
16:16:16 gmann in governance doc etc
16:16:21 bauzas damn, you beat me
16:16:26 gibi gmann: is there a global requiremnet fix up for it or should I push?
16:16:39 stephenfin and indicate on the bug if there are other failures other than nova-specs. Sounds like there are
16:16:49 gmann gibi: that was different i fixed few on governance repo but removed ext_link from election repo as thre were many to fix
16:17:18 gmann example #link https://review.opendev.org/c/openstack/governance/+/825257
16:17:29 bauzas stephenfin: I'm afraid we would need to modify our specs and docs in order to make them compliant with a foreseenable future of sphinx ?
16:17:45 gmann but that was for extlink in conf
16:17:47 stephenfin I don't think so. I think it's a bug
16:17:49 sean-k-mooney i think in this cae there was only 1 duplicate link
16:17:50 bauzas stephenfin: or does sphinx team said sorry it was an unwanted regression?
16:17:57 gibi gmann: ohh OK, so that is different
16:18:10 gmann there were many change in 4.4.0 which broke our existing doc
16:18:11 stephenfin doing e.g. [1] style referencing is a perfectly reasonable thing to do
16:18:13 bauzas stephenfin: ok, so bug it was, not a feature
16:18:36 bauzas stephenfin: we'll propose you a full-time job for fixing our docs then
16:18:40 stephenfin Both. It was a feature that was a breaking change
16:18:43 sean-k-mooney yep within a singel doc it shoudl be fine
16:18:46 gibi sean-k-mooney: nope, there are many, sphinx gave up parsing at the first duplicate
16:18:52 sean-k-mooney ah ok
16:19:07 sean-k-mooney so the "feature" was treating them a global link targets
16:19:12 sean-k-mooney not local to the current doc?
16:19:14 gibi sean-k-mooney: something like that

Earlier   Later