Monday, 2022-03-21

bauzashello Nova10:02
bauzasI'm surprised we won't need a RC2 release10:03
* bauzas tries to look at the open bugs10:03
bauzashttps://bugs.launchpad.net/nova/+bugs?field.tag=yoga-rc-potential is empty10:04
* kashyap waves hi10:06
bauzasmmmm10:10
bauzasactually, found https://bugs.launchpad.net/nova/+bug/196499510:10
bauzasdmitriis: adding the yoga regression tag to your BP10:10
bauzasonce sean-k-mooney is back, I'd like to understand whether it's a regression10:11
gibi_ptobauzas: vpd is a new thing in Xena isn't it? so that bug cannot be a direct regression, more like a limitation on the new feature 10:50
bauzasgibi_pto: welcome back if you are no longer on PTO10:51
bauzasgibi_pto: I don't know, I just saw the title so I added the tag10:51
bauzasbut I'll look at it later today10:51
gibi_ptobauzas: ~backish10:52
gibi_ptoI think I will be useless today10:52
* bauzas needs to prepare the lunch for her kid10:53
opendevreviewFelix Huettner proposed openstack/nova stable/queens: Gracefull recovery when attaching volume fails  https://review.opendev.org/c/openstack/nova/+/82986110:54
erlonbauzas: hey, when you have a chance can you look at my comment on bug 1944619? sean-k-mooney1 also said he would look it today, so I think we still can consider it to yoga12:02
sean-k-mooney1erlon: yep im just pulling down your patch locally im going to run the regression test a few times then ill review it12:51
*** sean-k-mooney1 is now known as sean-k-mooney12:51
sean-k-mooneyerlon: im not sure if this rises to the level fo an rc2 fix12:52
sean-k-mooneybut it can be fixed on master and then backported and released in 25.0.1 after the yoga offial release is done12:52
erlonright13:00
*** iurygregory_ is now known as iurygregory13:10
*** needssleep is now known as TheJulia13:13
*** dasm|off is now known as dasm13:29
sean-k-mooneyerlon: ok i have the first patch running with "tox -e functional  -- --until-failure 1944619" ill leave that runing for 10 mins while i review the patches and then ill do the same on the second patch. if both look stable and i see no issues with the patches ill re add my +213:44
sean-k-mooneyerlon: minor issue in https://review.opendev.org/c/openstack/nova/+/81532413:50
erlonlet me check13:51
sean-k-mooneyjust the fixme comment its now fixed13:51
erlonpw, tru, missed that one13:51
erlonlet me fix13:51
opendevreviewErlon R. Cruz proposed openstack/nova master: Fix pre_live_migration rollback  https://review.opendev.org/c/openstack/nova/+/81532413:54
sean-k-mooney cool im am runing htat version now ill leave it for 10 mins and then ill review it again13:55
sean-k-mooneythanks for updating it quickly13:55
bauzaserlon: sorry, but like I said in the bug report, it's not a regression so we can't fix it for yoga RC213:59
erlonbauzas: ok, I had forgotten about the RC policies, but sean suggested us to merge it on master and backport it14:00
bauzaserlon: yup14:00
bauzasbut we can only backport after Yoga release14:00
erlonright14:00
erlonit can wait14:00
erlonthanks for given attention to it14:01
sean-k-mooneythe test seams stable locally at least so i reinstated my +2 on both patches14:10
sean-k-mooneythe releas should be thrusday week so the back port can be done from april 1st once the master version is merged14:11
bauzassean-k-mooney: Yoga GA is on Wed next week14:21
bauzasie. March 30th14:22
sean-k-mooneyoh they are not going with the normal "thursday" fo the week convention14:22
sean-k-mooneyok14:22
bauzassean-k-mooney: they always release on Wednesdays14:22
bauzasthe GA, I mean14:22
sean-k-mooneyreally? ok didnt know that14:22
sean-k-mooneyi guess it give more time for press releases ectra14:23
bauzaslemme verify but I'm 99% on it14:23
bauzashttps://releases.openstack.org/xena/schedule.html#xena-release14:23
sean-k-mooneyi dont think it changes the math much. tl;dr we can start backporting after that release is done14:23
bauzashttps://releases.openstack.org/wallaby/schedule.html#wallaby-release14:23
bauzasetc.14:23
bauzaserlon: if I have time, I'll try to look at your change tomorrow14:24
bauzassean-k-mooney: have you seen my ping about https://bugs.launchpad.net/nova/+bug/1964995 ?14:24
bauzassean-k-mooney: not sure it's a regression14:24
erlonno, let me see14:26
bauzasI just added the tag to make sure we don't forget about it14:27
bauzasfor the moment, we don't have any needs for a RC214:27
bauzashttps://review.opendev.org/q/project:openstack/nova+branch:stable/yoga is super empty14:27
sean-k-mooneybauzas: am so vpd was added this cycle and it intoduced the bug14:27
bauzaselodilles: ^ for your knowledge14:28
sean-k-mooneyhowever nothing uses the network capablities14:28
sean-k-mooneyso to me its a regression but it wont break anything14:28
sean-k-mooneywe only merged half of the network capablities feature e.g. the reportign into the db we did not merge the other half that consumes that info14:28
sean-k-mooneybauzas: so i think that should be fixed but im not conviced we need an RC2 for it14:30
sean-k-mooneyits more tech debth then somethign that will break any user of nova14:30
bauzassean-k-mooney: if nothing was used in Xena, it's not a regression14:30
bauzassean-k-mooney: ok, so I'll remove the tag and I'll change the title14:31
sean-k-mooneyi was orginaly hoping to get that in rc1 by the way now that that has shiped i think it can just be a normal bugfix after the release14:31
bauzassean-k-mooney: yeah, we can merge any bugfix before RC1 but after, the ship has sailed14:37
bauzaslike erlon's bugfix14:37
bauzasthose are just policies for distro vendors and ops, which I can understand14:37
elodillesbauzas: sean-k-mooney: yepp, GA is always Wednesday (compared to milestone and other deadlines, which are on Thursdays)14:46
elodillesbauzas: ack, so we have one bug that does not need an RC2, as it seems now14:47
sean-k-mooneybauzas: can we retarget https://blueprints.launchpad.net/nova/+spec/cpu-selection-with-hypervisor-consideration to zed yet or do we need to wait15:10
sean-k-mooneyit looks like yoga is still set as the current branch in launchpad15:11
sean-k-mooneyi assume you are waitign till the actual release to swap it over15:11
sean-k-mooneyshould we add that blueprint to the meeting adgenda or wait untill after the release15:13
sean-k-mooneyelodilles: could you take a look at https://review.opendev.org/c/openstack/nova/+/828413/2 the follow up has +2+w and is waiting on the job being enabled15:22
elodillessean-k-mooney: hmmm, jobs aren't backported usually, and as I see it's non-voting15:29
sean-k-mooneywell we dont currently have coverage for hybrid plug in xena15:31
sean-k-mooneyit was the default before xena15:31
sean-k-mooneybut we did not readd it when we changed the devstack default15:31
sean-k-mooneyso this is really just add back coverage we had for wallaby to xena15:32
sean-k-mooneywhich we now have on yoga again15:32
elodilles(at least the new job nicely shows that the bug fix works)15:33
sean-k-mooneyit is non voting but it actully should get fliped to voting at some point15:33
sean-k-mooneyi think that is in the follow up patch15:33
elodillesyes, i see now15:33
sean-k-mooneyyep so we were using that like a regression test to demonstrate the issue15:34
elodillessean-k-mooney: +2+W'd, thanks for the details about the fix15:54
sean-k-mooney:) 15:56
bauzassean-k-mooney: I prepared the zed cycle 16:00
bauzassean-k-mooney: but actually I forgot to update the launchpad main branch16:00
artombauzas, sean-k-mooney, https://review.opendev.org/c/openstack/nova/+/806049/16:15
sean-k-mooneythanks :)16:17
bauzasfwiw, I'm about to give a go to https://review.opendev.org/c/openstack/nova/+/833440 as it won't harm our future tick-tock cadence16:52
bauzasthis is about removing Xena computes support for Zed 16:53
bauzasbut we definitely need to discuss this at the PTG16:53
gibi_ptobauzas: correct, we have to change that limitation in the future to support N-2 -> N upgrades17:30
bauzasI'll leave this change open until tomorrow and we'll discuss at the nova meeting17:31
sean-k-mooneygibi_pto: well that is the topic to discuss at the PTG apprently we dont actully have too but likely should17:31
sean-k-mooneygibi_pto: just repeating what i have heard but appretly live rolling upgrade supprot for n-2 is left to the projects to opt in too17:32
sean-k-mooneyso if we elect to supprot n-2 rolling upgrades upstream then we shoudl alter that check and add a job to validate it if we dont then we could keep it at n-117:33
gibi_ptoahh, OK, lets talk that through on the PTHG17:33
gibi_ptoPTG17:33
gibi_ptobauzas: that change fails in grenade on the service version check17:33
gibi_ptohttps://zuul.opendev.org/t/openstack/build/a24b974ae9fd487694724da795bfcd2a/log/controller/logs/screen-n-cond.txt#114017:34
dansmithbauzas: I think we should have something like this for nova: https://docs.openstack.org/cinder/latest/contributor/gerrit.html#ci-job-rechecks17:34
dansmithsome discussion of late in the tc about how most people just do blind rechecks all the time17:34
dansmithprobably don't need that much detail for nova given that we don't have all the drivers, but still, I see a lot of "recheck" with no explanation, which I think often means no inspection17:35
dansmithI'm hoping we'll have some general direction out of the tc about this, but would be nice to jumpstart in the nova community with reminders and constructive peer pressure :)17:35
gibi_ptodansmith: I suppor that idea!17:36
dansmithgibi_pto: I support your support :)17:37
sean-k-mooneywe used to have a section that said you should file a bug and add an elastic recheck query i think17:37
dansmithhowever, I do not support you spending pto hanging out in irc :P17:37
gmannlike neutron, we can monitor how many recheck for this week we had17:37
dansmithsean-k-mooney: yeah, but we need more constructive peer pressure regardless.. clear documentation to point to would be helpful when doing that17:38
gmanns/gibi_pto/gibi_pto_but_work_on_irc :)17:38
dansmithsean-k-mooney: if we've got it, then cool, but a concerted team-wide effort is needed I think17:38
dansmithgmann: paid time on work is just work :P17:38
gibi_ptonah, I just randomly hanging around :)17:38
sean-k-mooneydansmith: i think we removed it at som epoint im checking to see if we still do17:38
sean-k-mooneyi tought it was in https://github.com/openstack/nova/blob/master/doc/source/contributor/code-review.rst but not seeign it17:38
dansmithI can certainly write up some stuff17:40
sean-k-mooneyits also not in our testing doc https://github.com/openstack/nova/blob/master/doc/source/contributor/testing.rst so ya i think we remved it17:40
sean-k-mooneydansmith: this is proably where it need to be updated https://opendev.org/openstack/nova/src/branch/master/doc/source/contributor/process.rst#how-can-i-get-my-code-merged-faster17:47
sean-k-mooneywe currently say """If you're fixing something that only occasionally failed before, maybe recheck a few times to prove the tests stay passing."""17:48
sean-k-mooneybut we dont give guidnce on when its appropate to recheck in general17:48
gmanndansmith: or may be to writeup in project-team-guide and point projects doc to that ?17:48
sean-k-mooneygmann: we do link to this https://docs.opendev.org/opendev/infra-manual/latest/developers.html#automated-testing17:49
sean-k-mooneywe used to have a version fo that in nova17:50
gmannI mean to tell "no blind recheck" and 'best way to check logs and find issue' explicitly 17:50
sean-k-mooneystep 2 """Examine the console log or other relevant log files to determine the cause of the error. If it is related to your change, you should fix the problem and upload a new patchset. Do not use “recheck”."""17:50
sean-k-mooneywe do link to that form our testing.rst doc17:52
gmannyeah, I think due length of this doc it got hidden and people ignore to read the complete doc. we can add link to this doc for details but have a explicit section about recheck and how to use it in best way 17:53
gmanndur to17:53
sean-k-mooneyif we had a centralised one we coudl have zuul link top it when it fails17:53
sean-k-mooneyby updating the failure message17:54
sean-k-mooneyin any case it took me 5 mins to find that and i more or less know what im looking for so a new contibutor is likely not going to find it17:55
gmanntrue17:56
*** lajoskatona_ is now known as lajoskatona17:59
stephenfinsean-k-mooney: https://review.opendev.org/c/openstack/os-traits/+/833826 easy patch18:44
sean-k-mooneystephenfin: ah has the discussion on that been resovled18:47
sean-k-mooneyi saw the thread you started but did not keep track of it while i was off18:47
sean-k-mooneyoh its just the reference syntax in zuul. that keeps duplicaiton down at least.18:49
sean-k-mooneythe zuul change that is https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286/2/zuul.d/project-templates.yaml18:49
sean-k-mooneystephenfin: ok done.#18:54
stephenfinspot on, thanks!18:54
sean-k-mooneydid you also do os-resource classes18:57
sean-k-mooneystephenfin: dont see it here https://review.opendev.org/q/topic:add-python3-unversioned-jobs but i think its independent too https://github.com/openstack/releases/blob/master/deliverables/_independent/os-resource-classes.yaml18:59
stephenfinOh, my hacky script probably just missed that18:59
sean-k-mooneyi need to add a PTG topic about this by the way 19:00
sean-k-mooneywe might want to merge those back into placment19:00
sean-k-mooneywe have a cirular dep issue with testing and releases19:00
sean-k-mooneywe can either relax the test that assert the amount of traits/resouce classes or we can put them all in the same repo19:01
sean-k-mooneystephenfin: im going to go eat something. if you push a patch add me and ill look at it tomorrow19:02
opendevreviewStephen Finucane proposed openstack/os-resource-classes master: Update CI to use unversioned jobs template  https://review.opendev.org/c/openstack/os-resource-classes/+/83453719:02
stephenfinsean-k-mooney: Cool. It's there btw ^19:03
opendevreviewMerged openstack/os-traits master: Update CI to use unversioned jobs template  https://review.opendev.org/c/openstack/os-traits/+/83382619:04
gmannstephenfin I missed it for os-traits but please update setup.cfg too to reflect the tested versions https://review.opendev.org/c/openstack/os-resource-classes/+/834537 19:13
stephenfingmann: I'd rather not mix those two things though I'll admit they're related. Do we want to bump 'python-requires' also?19:14
gmannalso, like i mentioned in ML reply, I have added to remove the release specific templates itself which will fix all these issue and less work during releases https://etherpad.opendev.org/p/tc-zed-ptg#L10819:14
gmannstephenfin: yes we can bump python-requires also. They are related as if we do not test py3.6/7 then we should update it in classifier too.  19:15
gmannin zed release template we will do the same for branched repo also19:16
stephenfinOh, that's a good idea19:16
gmannin Zed: python-requires >= py3.8 and remove py3.6 and py3.7 from list19:16
stephenfin_Personally_, I'd question the value the classifiers bring. They aren't used by any tooling that I'm aware of, unlike python-requires. I wonder if we should get rid of them?19:17
gmannI think someone might be checking it from pypi doc but yes I do not have anyone asked about it explicitly 19:19
dansmithgmann: yeah, maybe some centralized docs would be good19:25
dansmithgmann: I definitely think we need PTLs to get the word out though19:25
gmanndansmith: +1 on PTL one. I like to neutron way to track it in their weekly meeting. that is something we can suggest PTL to do.19:26
gmannI have added it in TC+PTL PTG etherpad 19:27
dansmithyeah19:30
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily for a Gerrit patch upgrade and kernel update, but should return again shortly21:33
*** dasm is now known as dasm|afk21:45

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