Tuesday, 2023-09-05

opendevreviewOpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/nova/+/89164803:10
bauzassean-k-mooney: can you review https://review.opendev.org/c/openstack/nova/+/893462 ?08:38
*** ralonsoh_ is now known as ralonsoh08:41
sean-k-mooneyi need to leave fo a doctors approintment soon but ill take a look at it today08:49
opendevreviewMerged openstack/nova master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/nova/+/89164808:57
* bauzas disappears early this morning due to an appointment, but I'll be back in 2 hours roundly09:05
*** dmitriis is now known as Guest187109:12
opendevreviewDanylo Vodopianov proposed openstack/nova master: Packed virtqueue support was added.  https://review.opendev.org/c/openstack/nova/+/87607509:58
plibeauhello guys, I need your help on this change https://review.opendev.org/c/openstack/nova/+/861172 10:10
dvo-plvsean-k-mooney, dansmith Uggla sahid Hello, Mayby you will have a chance to review patchset https://review.opendev.org/c/openstack/nova/+/87607512:21
sean-k-mooneydvo-plv: unfortunetlly we are past feature freeze fo this cycle12:27
sean-k-mooneyi could take a look but it cant merge until next cycle after RC1 is cut so thats 2-3 weeks form now12:28
sean-k-mooneybauzas: unless we want to consider a FFE for ^12:29
sean-k-mooneyi was +2 on it a month ago12:29
sean-k-mooneyit would have been nice to land that but we are now out of time12:29
bauzasI'm not super happy to create a FFE for this due to https://review.opendev.org/c/openstack/nova/+/876075/23/nova/objects/image_meta.py12:30
dvo-plvI see,maybe it will be good to take a look, if you have new comments, we will have a time to fix until next cycle12:30
bauzasI'd prefer to look at it in two weeks, after RC1 while the 2023.2 branch is created and then master is for 2024.112:31
opendevreviewDanylo Vodopianov proposed openstack/nova master: Packed virtqueue support was added.  https://review.opendev.org/c/openstack/nova/+/87607512:39
opendevreviewDanylo Vodopianov proposed openstack/nova master: Packed virtqueue support was added.  https://review.opendev.org/c/openstack/nova/+/87607513:05
opendevreviewSylvain Bauza proposed openstack/nova master: doc: mark the maximum microversion for 2023.2 Bobcat  https://review.opendev.org/c/openstack/nova/+/89374214:20
opendevreviewSylvain Bauza proposed openstack/nova master: Update compute rpc alias for bobcat  https://review.opendev.org/c/openstack/nova/+/89374414:26
ygk_12345some of my nodes in an aggregate dont have the aggregate mapping in the placement db for those nodes14:26
ygk_12345is this a bug in nova ?14:26
ygk_12345i am trying to use the command "openstack resource provider aggregate list <resource-id>14:27
ygk_12345that is returning empty result for those nodes in that aggregate14:27
ygk_12345i tried placement syc aggregates also14:28
ygk_12345but no result14:28
ygk_12345*sync14:28
opendevreviewMerged openstack/nova master: Follow up for unified limits: PCPU and documentation  https://review.opendev.org/c/openstack/nova/+/89346214:36
opendevreviewSylvain Bauza proposed openstack/nova master: Add service version for Bobcat  https://review.opendev.org/c/openstack/nova/+/89374914:41
ygk_12345any idea anyone ?14:49
dansmithygk_12345: not really enough information to say (like which release are you running?) but in general the placement aggregates should match the nova ones, yes14:50
ygk_12345dansmith: it is yoga14:51
ygk_12345the aggregate matching ismissing for one set of nodes in the az14:52
dansmithygk_12345: and that set of nodes is different how?14:53
ygk_12345dansmith: they are just added to the az along with others14:54
ygk_12345do I need to manually add all these nodes from that aggregate to match that aggregate using the command openstack resource provider aggregate set ?14:56
ygk_12345it succeeded for one node now14:56
dansmithygk_12345: when you add a node to an aggregate in nova, it should mirror that to placement for you14:56
ygk_12345but why did not it add those nodes automatically ?14:56
ygk_12345dansmith: but it did not do so for an aggregate14:57
*** dasm is now known as Guest192914:57
dansmithygk_12345: not sure what to say without logs and things... try removing it from the aggregate in nova, re-add it and look at the nova-api logs to see if there's a failure talking to placement or something14:58
ygk_12345dansmith: ok14:59
bauzasreminder: nova meeting in 1 hour15:00
bauzasygk_12345: we have some method that calls placement for creating the same aggregates, sec15:00
ygk_12345bauzas: ok15:01
ygk_12345bauzas: please let me know15:01
*** Guest1929 is now known as dasm15:02
bauzaseventually found the change https://review.opendev.org/c/openstack/nova/+/55359715:04
ygk_12345bauzas: I have removed and re added and now it is working. Thank you15:07
bauzasok good to know15:07
dansmithygk_12345: that likely means nova-api wasn't able to talk to placement at the time you added those nodes originally, for whatever reason15:09
ygk_12345dansmith: seems so. Thanks for your time and patience15:09
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Sep  5 16:00:02 2023 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
bauzaswelcome folks16:00
gibio/16:00
sean-k-mooneyo/16:00
Ugglao/16:00
elodilleso/16:00
auniyalo/16:00
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:00
dansmitho/16:00
bauzascool, people arriving fast, lovin'16:00
bauzaslet's start16:00
bauzas#topic Bugs (stuck/critical) 16:00
bauzas #info No Critical bug16:01
bauzaswhoops16:01
bauzas#info No Critical bug16:01
bauzas#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 49 new untriaged bugs (+0 since the last meeting)16:01
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:01
bauzas#info bug baton is bauzas16:01
auniyalbauzas, I have few bugs to discuss16:01
bauzasauniyal: any questions you have ?16:01
bauzascool, shoot16:01
auniyalactully this : https://etherpad.opendev.org/p/nova-bug-triage-2023090216:02
bauzasack, looking16:02
auniyalhttps://bugs.launchpad.net/nova/+bug/2031635:16:02
auniyalack16:02
bauzasI'm not expert, I can't tell16:03
auniyalI'll paste the quick ones here16:04
auniyalhttps://bugs.launchpad.net/nova/+bug/2033393: Xena:  server name is not updated in guest xml after rename ?16:04
gmanno/16:04
gibiso for 2031635 we need to check if https://review.opendev.org/c/openstack/nova/+/867788 is backported to stables or not16:04
auniyalis it known ? does it does affect an operation16:05
bauzaslet's not discuss the resolution here16:05
auniyalgibi, its not backported16:05
gibiauniyal: then I guess we need to backport it16:06
gibias we need to support py3.816:06
auniyalack,16:06
bauzasok, resolution set, Valid then16:06
bauzaswe can look at the other ones next week16:06
dansmithauniyal: the instance name one is invalid, I just updated16:07
auniyalack, thanks dansmith16:07
bauzasok, let's move on then16:07
bauzas#topic Gate status 16:08
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:08
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status16:08
bauzas#info nova-emulation is still b0rked16:09
bauzaschateaulav: are you around ?16:09
sean-k-mooneyoh really16:09
sean-k-mooneyi was not aware of that16:09
sean-k-mooney whats broken16:09
sean-k-mooneytest_resize_volume_backed_server_confirm16:10
sean-k-mooneyso that might not be related to emulation16:10
sean-k-mooneythe other tests passed16:10
dansmithyeah not sure why that would be emulation related16:10
dansmithother than that it can be slow16:10
sean-k-mooneyill quickly take a look async16:11
bauzasyeah probably unrelated, but alas this is the only one which fails every week16:11
sean-k-mooneyno obvious error in the nova log16:11
gmannand a few of the fixes are merged related to this test but yes it can fail on slow maybe16:11
bauzasokay, so we'll see if next round it fails again16:12
bauzasany other gate information to share ?16:13
dansmithotherwise I think the gate is doing better than it has in a while16:14
dansmithwe still need volume test attention like we have for many years16:14
dansmithbut life isn't as terrible as it has been16:14
bauzasglad to hear such good news16:15
bauzaswhich weren't arriving just because of luck16:15
bauzasso kudos to those who worked hard on chasing 16:15
bauzasmoving on then16:16
bauzas#topic Release Planning 16:16
bauzas#link https://releases.openstack.org/bobcat/schedule.html16:16
bauzas#info Nova deadlines are set in the above schedule16:16
bauzas#link https://etherpad.opendev.org/p/nova-bobcat-blueprint-status Etherpad for tracking blueprints status16:16
bauzas#info 9 blueprints were implemented this cycle, 8 got deferred (5 of them were awaiting rebases from owner)16:16
bauzasthanks folks who reviewed features16:17
sean-k-mooneyjust on last thing on nova-emulation. we didn not pin that job to < 6 concurancy so maybe we need to drop that back to 416:17
bauzasdespite a very few of happy reviewers, we were able to merge a quite decent number of reviews16:17
bauzass/reviews/changes16:17
gmannsean-k-mooney: but is it oom issue happening there?16:17
sean-k-mooneyi dont think so ill look after the meeting16:18
sean-k-mooneyi just assume since this is testing qemu with emulation of arm it might be slower16:18
sean-k-mooneyanyway we can go back to the release topic16:18
gmannack16:19
bauzassean-k-mooney: thanks 16:19
bauzasso, I was just saying thanks 16:19
bauzaswe 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
sean-k-mooneythere was one that kind fo fell in that camp16:20
bauzaswe still have two long series that require proper attention next cycle if they're reproposed, as those series are very long and hard to review16:20
sean-k-mooneythe virtio-packed ring format16:20
bauzasit was in merge conflict until last week16:21
bauzasactually, until today16:21
sean-k-mooneyno it ws mergable a mount ago16:21
bauzasso no, it was still on the camp "the owner has to do things"16:21
sean-k-mooneyand then went int merge conflcit in between16:21
bauzassure16:21
sean-k-mooneyi had tought we merged it16:22
bauzasbut I raised a couple of times the fact that we are requiring a correct state of a patch for being reviewed16:22
sean-k-mooneyit was kasyaps min version bump that caused the merge conflict16:22
bauzasand it was correctly tracked in the etherpad as being 'in merge conflict'16:22
bauzassean-k-mooney: I bet no, since it was on merge conflict *before* we merged the min version bump16:22
bauzasbut I can doublecheck the timings based on the etherpad history16:23
sean-k-mooneyanyway im sad that missed but  it is what it is16:23
dansmithyeah I think it was in merge conflict before16:23
bauzasagain, that one was correctly tracked and marked as not reviewable yet16:23
sean-k-mooneyi had put review priorty +2 on it for what its worth16:23
sean-k-mooneyi think part of the miss there may have been pto related16:24
bauzasso, I 'm against granting an exception for it (and even not considering the object version change, which is kinda huge to consider)16:24
sean-k-mooneyim not asking for one16:24
sean-k-mooneybut i i had realised it was not merged last week i would he pinned them to update it16:25
bauzaswe're providing weekly meeting updates for such concerns16:25
bauzasI can't just ping every single owner to ask him or her to update16:25
bauzasit was tracked, an action was awaited16:25
bauzasanyway, like I said a couple of hours before, a reproposal is surely acceptable for 2024.1 and can be reviewed in 2 weeks, once master becomes Caracal16:26
sean-k-mooneyyep16:26
sean-k-mooneywe also shoudl have landed https://review.opendev.org/c/openstack/nova/+/860829 by the way16:27
sean-k-mooneythat is needed for the swithc to sqlalchme 216:28
bauzasthis isn't a feature, and according isn't impacted by FF16:28
bauzasso it can be reviewed now until RC116:28
dansmithit's also not release critical for 2023.2 AFAIK16:28
bauzasand which gives me the right opportunity to jump to the next item16:28
bauzas#info 1 week before RC116:28
bauzas#link https://etherpad.opendev.org/p/nova-bobcat-rc-potential Etherpad for tracking RCs16:28
bauzasif people would enjoy clicking on such link (exactly like they hopefully did for the feature tracking etherpad just before),16:29
bauzasthey'll see that there are a couple of paperwork-ish but important changes to deliver before RC116:29
bauzasmostly for upgrade concerns (rpc aliases and object version tagging)16:30
bauzasin that etherpad, people are fancy adding patches if they feel that require to be merged before RC116:30
bauzasbut, I'll ping people anyway asking for reviews16:32
bauzasI haven't yet prepared a bobcat tag for bug reports, I'm just doing it now16:33
bauzasthere16:34
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=bobcat-rc-potential feel free to tag any bug report with this tag in order to have it tracked for RC1 and post-RCs16:34
opendevreviewJay Faulkner proposed openstack/nova master: [FUP] [ironic] Fix for mutable nova-cpu configs  https://review.opendev.org/c/openstack/nova/+/89379016:34
bauzasmoving on16:35
bauzas#topic Review priorities 16:35
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+OR+label:Review-Priority%252B2)16:35
bauzas#info As a reminder, people eager to review changes can +1 to indicate their interest, +2 for asking cores to also review16:35
bauzas#topic Stable Branches 16:35
bauzaselodilles: tell the good news16:35
elodilleso716:35
elodilles#info stable/train is marked as End of Life and branch is deleted16:35
bauzas\o/16:35
elodilles#info all stable gates should be OK16:35
bauzas\o/16:36
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:36
elodillesplease add there gate issues if you encounter one ^^^16:36
elodillesand that's all from me16:36
sean-k-mooneyelodilles: what was the result of testing os-vif stable16:36
bauzasthanks elodilles16:36
sean-k-mooneydid the job fail? i.e. should i look at why or did it pass on your DNM patch16:37
elodillessean-k-mooney: let me check it quickly16:37
sean-k-mooneyno rush16:37
sean-k-mooneyif it failed i can try and take a look at why later16:37
bauzasauniyal: you had other items to mention16:37
elodillessean-k-mooney: gate tests have passed16:37
sean-k-mooneysweet16:37
auniyal#info Please{10} *review* these backport patches of stable 2023.1, zed and yoga for next minor release16:38
auniyal#info most of these already have one +2.16:38
auniyal#link https://etherpad.opendev.org/p/release-liaison-PatchesToReview16:38
auniyalthanks 16:38
bauzascool, will try a round tomorrow16:38
bauzassounds to me it's important to deliver a 2023.1 release shortly16:39
bauzas#topic Open discussion 16:39
bauzasnothing on the agenda, anything anyone ?16:39
bauzasok, looks not16:42
bauzasthanks everyone16:42
bauzassee you next week16:42
bauzas#endmeeting16:42
opendevmeetMeeting ended Tue Sep  5 16:42:12 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:42
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2023/nova.2023-09-05-16.00.html16:42
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-09-05-16.00.txt16:42
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2023/nova.2023-09-05-16.00.log.html16:42
elodillesthanks o/16:42

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!