Thursday, 2022-03-10

opendevreviewArtom Lifshitz proposed openstack/nova master: Update PCI requests in request spec on resize  https://review.opendev.org/c/openstack/nova/+/80604900:39
*** dasm|bbl is now known as dasm03:06
*** dasm is now known as dasm|off04:08
*** abhishekk is now known as akekane|home04:56
*** akekane|home is now known as abhishekk04:56
elodillesmelwitt: thanks! :)05:50
opendevreviewJorhson Deng proposed openstack/nova master: remove some redundant parameters in migrate_server  https://review.opendev.org/c/openstack/nova/+/80814307:12
opendevreviewJorhson Deng proposed openstack/nova master: remove some redundant parameters in migrate_server  https://review.opendev.org/c/openstack/nova/+/80814307:14
EugenMayerHello, out of a 'sudden' when deploying a series of VMs ussing terraform on openstack (spawning a k8s cluster of 4 nodes) some of them (usually 1) stucks in 'spawning' mode in openstack. We did this about 50 times already before, so it was working flawlessly - but suddenly it broke. What tools would i have to understand why they are in the07:22
EugenMayer'spawning' state and what hinders the VM to actually spawn?07:22
gibibauzas: hi! prelude looks good to me. do we still wait for other +2s or should I just approve it08:17
gibi?08:17
gibiEugenMayer: you have to track down what step that VM failed. I would first look at the conductor logs for error and the log of the nova-compute where the VM is scheduled to.08:19
opendevreviewOpenStack Release Bot proposed openstack/placement stable/yoga: Update .gitreview for stable/yoga  https://review.opendev.org/c/openstack/placement/+/83297908:21
opendevreviewOpenStack Release Bot proposed openstack/placement stable/yoga: Update TOX_CONSTRAINTS_FILE for stable/yoga  https://review.opendev.org/c/openstack/placement/+/83298108:21
opendevreviewOpenStack Release Bot proposed openstack/placement master: Update master for stable/yoga  https://review.opendev.org/c/openstack/placement/+/83298308:21
opendevreviewOpenStack Release Bot proposed openstack/placement master: Add Python3 zed unit tests  https://review.opendev.org/c/openstack/placement/+/83298508:21
bauzasgibi: hey, maybe we can hold it until noon08:25
kashyapCompletely aside, TIL: with Py 3.7, "breakpoint()" is now an alternative to "import pdb ; pdb.set_trace()"08:25
gibibauzas: OK08:28
gibikashyap: ohh, nice. then I TIl that today too :)08:28
bauzasgibi: do you know if someone already provided a nova change for using the new grenade-skip-level job ?08:29
bauzasgibi: if no, I'll do it08:29
kashyapgibi: https://peps.python.org/pep-0553/ :)08:29
kashyapSee the 4 points in the Rationale section08:30
gibibauzas: I only see this https://review.opendev.org/q/topic:test-grenade-skip-level08:30
gibithat adds the job the check queue08:31
EugenMayergibi thank you. Which logs would you look for on the conductor?08:31
EugenMayergibi i think the candidate is https://gist.github.com/EugenMayer/db07bf3ecc8bad464afb0040700d644d08:33
bauzasgibi: oh right, I forgot about it08:36
bauzashttps://review.opendev.org/c/openstack/tempest/+/830670/1/zuul.d/integrated-gate.yaml we test it for the whole integrated gate08:36
gibiEugenMayer: yeah that means that service could not communicate with keystone08:36
EugenMayergibi are there somewhat rate limits or not? I guess it uses the LB to do that and it might be somewhat saturated. I could not understand why this suddently (but consistently) happens08:37
gibiEugenMayer: [Errno 113] EHOSTUNREACH seems to be a network connection error to me08:38
EugenMayerSeems so, but how could that happen out of a sudden, that's odd. Running xena with OVN here.08:39
gibikashyap: I could have been the author of this PEP :)08:40
kashyapgibi: Haha, I'll believe you08:40
gibiforgetting the semicolon08:40
gibithat is typical :)08:41
gibiEugenMayer: I have not furter ideas what can cause that. I suggest you to troubleshoot your network infra. 08:44
EugenMayergibi well the entire infra is based on OVN / openstack .. that's my issue here. You assume asking over in neutron what could cause this, right?08:47
EugenMayer(or how to track it down)08:48
gibiEugenMayer: yeah you can try over there too08:48
EugenMayerThank you!08:49
EugenMayergibi isn't it odd alltogether that this happens, since the conductor is running on the controller itself?08:49
EugenMayergibi even the load-balancer that it is offered via is running on the controller, the host where actually the conductor uns on08:50
gibiyeah it is definetly odd08:50
bauzasdamn, we're playing against Zuul by now09:56
bauzassean-k-mooney: we have 2 open bug reports for RC1 https://bugs.launchpad.net/nova/+bugs?field.tag=yoga-rc-potential that relate to https://review.opendev.org/c/openstack/nova/+/82857009:58
bauzassean-k-mooney: given I don't see your +2 for the main change, can we punt https://bugs.launchpad.net/nova/+bug/1949808 and https://bugs.launchpad.net/nova/+bug/1960412 off the RC1 ?09:59
bauzashumpf, this looks sad we no longer have translations https://review.opendev.org/q/topic:zanata%252Ftranslations10:07
bauzaslast one we had was in ussuri https://review.opendev.org/c/openstack/nova/+/72316010:07
bauzasmy bad, xena10:08
opendevreviewkiran pawar proposed openstack/nova master: VMware: Split out VMwareAPISession  https://review.opendev.org/c/openstack/nova/+/83215610:41
opendevreviewkiran pawar proposed openstack/nova master: VMware: StableMoRefProxy for moref recovery  https://review.opendev.org/c/openstack/nova/+/83216410:41
noonedeadpunkhey there! I have issue that is kind of related to https://bugs.launchpad.net/nova/+bug/177856310:48
noonedeadpunkso mdev get re-crearted and allocated during migration. But I guess nothing has been done when compute host got rebooted?10:49
noonedeadpunkSo with compute reboot mdev device are gone, so nova-compute jsut refuse to start10:50
noonedeadpunkwith https://paste.openstack.org/show/b5m5sW2194PRjd2hLGtg/10:50
noonedeadpunkso basically on nova-compute start we need to ensure that devices exist same way we do during migration I guess?10:51
noonedeadpunkit's on V just in case, so not sure maybe it's already fixed on later branches10:52
gibinoonedeadpunk: I think it is an open bug https://bugs.launchpad.net/nova/+bug/190080011:08
noonedeadpunkoh, mdevctl define, nice, thanks!11:10
gibinoonedeadpunk: happy to help :)11:11
noonedeadpunkgibi: I wonder if it's worth to mention it on https://docs.openstack.org/nova/latest/admin/virtual-gpu.html#caveats ?11:18
gibinoonedeadpunk: good point. I think it would be good to list it there. If you have time please push a small doc patch. 11:19
sean-k-mooney[m]we dont currenlty use mdevctl and if we wer too we would have to basically re write how we do mdev management11:23
sean-k-mooney[m]today we expect nova to creat the medevs after a host reboot11:24
sean-k-mooney[m]when it recreates the vms11:24
sean-k-mooney[m]if we want to use mdev ctl in the future we need to strart tacking mdevs like pci devices or pmem11:24
noonedeadpunkbut it doesn't?11:24
noonedeadpunkI mean - nova jsut crash11:25
sean-k-mooney[m]it should when you start the vm11:25
sean-k-mooney[m]the current bug is just that a bug11:26
noonedeadpunkhm... maybe it's result of resume_guests_state_on_host_boot then...11:26
sean-k-mooney[m]maybe11:26
noonedeadpunkAs what I see when trying to start nova-compute - crash with https://paste.openstack.org/show/b5m5sW2194PRjd2hLGtg/11:26
noonedeadpunkSo to start nova compute I need mdev to be created11:26
noonedeadpunkNeed to try dropping resume_guests_state_on_host_boot indeed11:27
sean-k-mooney[m]bauzas:  wasnt there someone already working on a fix for that ^ by the way11:31
sean-k-mooney[m]i remember talking to you about fixing it a few months ago but dont recall if you strated to impelent it but wasnt someone else looking at fixing the issue11:31
sean-k-mooney[m]@noon11:32
sean-k-mooney[m]noonedeadpunk: the issue i have with mdevctl is that nova expect that the mdevs do not exist in the normal code path11:32
sean-k-mooney[m]so if you just precreate arbitary mdevs it will break the ablity to create vms11:33
sean-k-mooney[m]and as a a tool it has little other utility if all you are doing is rectateing the mdevs used by the existing vms11:33
sean-k-mooney[m]creating an mdev is just echoing a uuid into a file in /sys11:34
sean-k-mooney[m]mdevctl also used to not be pakaged on anything other then fedora https://repology.org/project/mdevctl/versions its a little better now as tis actull in debian and ubuntu too but its not a tool that you could previously rely being in your distro package11:37
noonedeadpunkwell, I had other issue, but maybe because in the region we run V11:37
dmitriisgibi: o/ Apologies for an extra ping, just wanted to ask if you're good with https://review.opendev.org/c/openstack/nova/+/829974 since you've reviewed it before.11:38
dmitriisNot sure if it's appropriate to land it at this point or not but that's more of a fix + test change rather than a new feature.11:38
noonedeadpunkSo to start nova-compute we indeed had to echo uuid to /sys11:38
sean-k-mooney[m]ya that is the workaround for now11:39
noonedeadpunkbut it's hard as you need to get resource from placement to understand mapping of uuid to mdev pci device11:39
sean-k-mooney[m]i prefer recommendign that as its safer then mdevctl11:39
sean-k-mooney[m]yes as i siad i tought someone had wirtten that up11:39
noonedeadpunkyeah, I see11:40
sean-k-mooney[m]i know bauzas started at one point11:40
sean-k-mooney[m]i remember discussing the algrothim with them and how they would have to use placement to find the parent pci device to know whic device to create the mdev on since that is not in the xml11:41
noonedeadpunkwell another weird thing is that mdev uuid is just random thing, while tbh I'd expect it to be resource uuid. Which would make things easier...11:42
noonedeadpunkAs we have resource uuid and then mdev uuid is just another thing that is stored _only_ in xml11:44
noonedeadpunk(in case I'm not missing anything11:44
sean-k-mooney[m]its randome because we do not track them in the db11:44
gibidmitriis, sean-k-mooney[m], bauzas: I'm generally OK with https://review.opendev.org/c/openstack/nova/+/829974 I do noted that this patch is now wide the gap we need to close later as part of https://bugs.launchpad.net/nova/+bug/1961587 as it adds more sysfs calls to our neutron code. 11:45
sean-k-mooney[m]i have been trying to change that since before we actully added the mdev feature11:45
sean-k-mooney[m]noonedeadpunk:  what i would like use to evolve to is have operators precreat the mdevs and we would track them in the resouces table in the db11:46
sean-k-mooney[m]then claim and allocate them to instances11:46
sean-k-mooney[m]or tack them in the pcidevice table11:47
sean-k-mooney[m]part of the reason i want to do that is i want to get rid of the persitnt libvirt domain xml11:47
sean-k-mooney[m]right now vgpus are the only thing that need to the persitent domain xml11:47
dmitriisgibi: ack, I am going to look at changing this to use extra info instead in a follow-up11:48
noonedeadpunkwell, I wasn't having much fun with plain qemu without libvirt, as if you don't need config you can jsut operate qemu directly?11:48
noonedeadpunktbh for me from operator prespective is preferable that nova manage mdev creation. as otherwise there will be tons of nasty hooks which everybody do. This can be handled by deployment tools ofc, but considering devices are not persistant and drop on reboot... dunno.11:50
noonedeadpunkand if uuid for mdev will be taken as placement resource id - wouldn't it solve issue with persistant libvirt config?11:51
noonedeadpunkas at time mdev is created, I guess allocation should be already claimed and resource provided where to create it?11:52
gibidmitriis: ack, thanks11:52
sean-k-mooney[m]noonedeadpunk:  you can have multiple mdevs attached to a vm so we cant use placemnt ids for the uuid11:57
sean-k-mooney[m]also they have to be gloally unique11:58
noonedeadpunkah, indeed, if it's not Nvidia Ampere that would be the case...11:58
noonedeadpunk(as there you have resource per vGPU)11:58
sean-k-mooney[m]removing the persitent domain is not the same as raw qemu11:58
sean-k-mooney[m]libvirt has 2 domains for each insthace11:59
sean-k-mooney[m]the running one in memory and an xml file on disk11:59
sean-k-mooney[m]on ocation they get out of sync and cause issues in managing the vm11:59
sean-k-mooney[m]so i would like to get rid of the file on disk and just use the in memory one which is the acurrate one12:00
noonedeadpunkyeah, I do agree herem that makes sense12:00
noonedeadpunkjust sugested that it could be first step to raw qemu, as had to deal with such solution on some cloud platform12:01
sean-k-mooney[m]if you have a patch or code to recreate the mdevs on boot using placement we would be happy to include it12:01
sean-k-mooney[m]are you in favor of raw qemu or against?12:02
noonedeadpunkI'm not at the moment as just found that out during incident, but will try to allocate some resources12:02
noonedeadpunkI'm personally against :)12:02
sean-k-mooney[m]ack just checkign libvirt does some useful stuff for us12:02
sean-k-mooney[m]so we are not currently plannig to remove it12:02
noonedeadpunks/just suggested/just assumed/12:02
sean-k-mooney[m]we dont really want to have to manage cgroups directly for example12:03
noonedeadpunkI guess it prings in selinux/apparmour rules as well12:03
noonedeadpunk*brings12:03
sean-k-mooney[m]yes12:03
sean-k-mooney[m]it deals with selinux lables and a bunch of other things which we dont want to have to implement in nova12:04
noonedeadpunkand some live migration features iirc12:04
sean-k-mooney[m]yes libvirt does the cpu compatiblity check for us12:04
sean-k-mooney[m]so removing the xml on disk simple. removign libvirt is basicaly a full rewrite of the dirver12:05
sean-k-mooney[m]which is not something we have time for or really want to do12:05
noonedeadpunkexeprience with raw qemu was quite painful12:05
sean-k-mooney[m]the only real advantage to raw qemu would be if libvirt did not have support for feature x yet12:06
sean-k-mooney[m]and at this point nova does not move fast enough for that to be an issue12:06
noonedeadpunkjust wanted to say the same:)12:07
noonedeadpunkvirtiofs great example of feature ppl love to get but nobody has capacity to help on with...12:07
sean-k-mooney[m]actully that is on our radar12:08
sean-k-mooney[m]it should hopefully get added in z12:08
sean-k-mooney[m]for manilla shares12:09
sean-k-mooney[m]but if you have other usecases for it let us know12:09
sean-k-mooney[m]once we have the basic support in the libvirt driver we can extend it simply if cyborg or anything else wants to use it12:10
sean-k-mooney[m]brb12:10
gibibauzas and others: I think we have a functional test instability https://paste.opendev.org/show/btHI7ErFfhKYFGdfoujl/12:12
gibie.g.: https://6779a19d629122a2ad74-09e4be48fe62aca6e4b03d954e19defe.ssl.cf1.rackcdn.com/828570/8/check/nova-tox-functional-py38/99a1e4f/testr_results.html12:12
gibirecently I saw this pretty frequently but It happened in the past too (I saw matches from mid february)12:13
gibiIm filing a bug...12:14
gibihttps://bugs.launchpad.net/nova/+bug/196447212:20
gibiohh the failing testcase was added here https://review.opendev.org/c/openstack/nova/+/82184012:33
gibithis is one of the bug with rc1 tag, where the fix is still open12:33
gibiso I guess the regression test added here is not stable and needs some tuning12:34
gibibauzas, sean-k-mooney[m] should we pull https://review.opendev.org/c/openstack/nova/+/815324/10 from the gate?12:35
gibior we expect a followup to stabilize the functional test in that?12:35
sean-k-mooney is it unstable12:41
sean-k-mooneyoh the regerssion12:41
gibithe test case is unstable12:42
sean-k-mooneyi see is it still unsable with the followup12:42
gibiwe only have data about it being unstable without the fix for the origina bug12:43
gibithat bugfix is on the gate12:43
gibiI tried to reproduce it locally but failed so far12:43
sean-k-mooney In the last 7 days from 8 failed functional test run 6 was due to this in nova. But this happened as far back as 14th of February.12:43
sean-k-mooneyso the test has only merged yesterday12:43
sean-k-mooneyso those other failures would have been on the path itself12:44
sean-k-mooneyas in https://review.opendev.org/c/openstack/nova/+/821840/5 merged yesterday 12:44
gibithe test case merged on the 5th12:44
gibioh no12:44
gibiit is 9th12:44
gibiyou are correct12:45
gibisorry12:45
gibiand you are correct before yesterday it is only failed on 821840/512:45
gibiafter the merge it is failed on 3 other pathes12:45
gibisee https://paste.opendev.org/show/btHI7ErFfhKYFGdfoujl/12:45
sean-k-mooneythen ya we shoudl either revert or disable i guess12:46
opendevreviewMerged openstack/nova master: Add functional tests to reproduce bug #1960412  https://review.opendev.org/c/openstack/nova/+/83001012:46
gibiyeah, no point yanking the bugfix from the gate as that does not break anyithing, the patch that added the test case was already merged12:47
gibiI can push a patch skipping the test case12:48
opendevreviewBalazs Gibizer proposed openstack/nova master: Skip TestRollbackWithHWOffloadedOVS.test_rollback_pre_live_migration  https://review.opendev.org/c/openstack/nova/+/83307912:52
gibibauzas, sean-k-mooney: ^^12:52
sean-k-mooneygibi: sorry was making coffee did you determin why its unstable by the way? i did not fully read your bug report13:01
gibisean-k-mooney: no, I had not time to actually look deeply into it. I has not been able to reproduce it locally yet. 13:01
gibi*was not able13:02
sean-k-mooneyok its odd the test is pretty simple13:03
sean-k-mooneyi mean for a live migration test13:03
sean-k-mooneygibi: did you mean to put that patch on top of master rather then the fix13:05
sean-k-mooneyactully i guess that makes sense too13:05
sean-k-mooneyif noone else reviews the skip by the end of the day ill fast approve to make sure its included in rc113:07
gibisean-k-mooney: thanks13:07
sean-k-mooneythe followup failed grenade by the way13:08
gibiI have some calls this afternoon, so I'm not sure I will have time to figure out today why it fails13:08
bauzasgibi: sean-k-mooney: sorry was afk, a tl;dr ?13:11
bauzasgibi: I see your comment on https://review.opendev.org/c/openstack/nova/+/815324/1013:12
gibibauzas: the functional test added here  https://review.opendev.org/c/openstack/nova/+/821840  is unsatble13:12
gibiso I pushed https://review.opendev.org/c/openstack/nova/+/83307913:12
gibithe we can figure out the stability issue13:12
gibi*then13:12
bauzasgibi: maybe we should revert the functional test then13:12
bauzasgibi: hah13:13
gibibauzas: we can do that as well, revert the func test and the revert the fix13:13
bauzasgibi: yeah I think it's better13:13
bauzasgibi: can you revert it ?13:13
bauzaserlon is not around13:13
gibiI can 13:13
bauzasthanks13:13
opendevreviewBalazs Gibizer proposed openstack/nova master: Revert "Adds regression test for bug LP#1944619"  https://review.opendev.org/c/openstack/nova/+/83290213:14
gibibauzas, sean-k-mooney: ^^ revert then13:14
sean-k-mooneyok that works for me too13:15
sean-k-mooneyalthough it would still be nice to fix this this cycle but i guess we can backport13:16
sean-k-mooneyi assuem we dont want to pull this into an RC2 right13:16
sean-k-mooneysince tis not really a regression form this cycle13:16
sean-k-mooneyits just a bug in the orginal sriov live migration feature13:17
sean-k-mooneyso it can wait and be backported as normla13:17
bauzassean-k-mooney: given the issue is not a regression it can't be a RC2 one13:18
bauzassean-k-mooney: but I'm OK to backport it to 25.0.1 once we open it13:18
bauzasthis is just, we're close to RC1 deadline and erlon isn't around13:18
sean-k-mooneyyep that is what i was thinking too13:19
bauzasgib: iI can't find the nova doc where we agree on having a quick and single +2/+W for reverts13:20
sean-k-mooneyi can get it but i +w it13:20
sean-k-mooneyso there is https://github.com/openstack/nova/blob/master/doc/source/contributor/policies.rst#reverts-for-retrospective-vetos13:21
sean-k-mooneybut i tought we had something else too13:22
sean-k-mooneyya i dont see anything else relevent13:24
sean-k-mooneyin anycase i think we can agree that reverting a regression test that is unstable is ok given the followup fix has not merged yet13:25
gibiI agree that fixing the gate is enough reason to quick approve a revert13:35
gibi(or a test skip patch)13:35
bauzasgibi: anyway, sean found the doc but also +Wd it13:36
sean-k-mooneythree cores walk into a bar, first core submits a patch to fix it, second core approves, third core say ouch how put this bar here13:39
gibi:D13:39
* sean-k-mooney is just sad that its been soo long since three cores actully did walk into a bar at a ptg or otherwise13:42
gibiyeah13:43
opendevreviewMerged openstack/nova master: Fix migration with remote-managed ports & add FT  https://review.opendev.org/c/openstack/nova/+/82997413:50
bauzassean-k-mooney: indeed, I missed bars, I'm so foo13:59
sean-k-mooneylol :)13:59
*** dasm|off is now known as dasm14:00
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs(db+object)  https://review.opendev.org/c/openstack/nova/+/83119314:00
opendevreviewribaudr proposed openstack/nova master: [WIP] Attach Manila shares via virtiofs(manila abstraction)  https://review.opendev.org/c/openstack/nova/+/83119414:00
opendevreviewribaudr proposed openstack/nova master: [WIP] Enable and use COMPUTE_STORAGE_VIRTIO_FS and COMPUTE_MEM_BACKING_FILE traits.  https://review.opendev.org/c/openstack/nova/+/83309014:00
sean-k-mooneynoonedeadpunk: ^ see virtio-fs work14:01
bauzassean-k-mooney: are you ok with me removing the yoga-rc-potential flag ? https://bugs.launchpad.net/nova/+bug/1960412 and https://bugs.launchpad.net/nova/+bug/1949808 ?14:01
sean-k-mooneyyes although the fix should hopefully merge shortly14:02
bauzasoh wait indeed14:03
bauzashaven't seen gibi voting14:03
noonedeadpunkoh, wow14:03
bauzaswe can hold14:03
sean-k-mooneyit failed on the flaky func test14:03
gibiyeah I found out about the flaky test by reviewing that other bugfix :)14:04
gibiohh it failed again :/14:04
gibithen we need the revert first14:05
sean-k-mooneyath least this time its looking ok https://zuul.openstack.org/status#82857014:05
sean-k-mooneynot that im watching it on my other monitor right now or anything14:05
sean-k-mooneytottally not14:05
gibi:)14:06
opendevreviewMerged openstack/nova master: Revert "Adds regression test for bug LP#1944619"  https://review.opendev.org/c/openstack/nova/+/83290214:16
bauzasgibi: I guess we can +W https://review.opendev.org/c/openstack/nova/+/83229215:04
bauzassean-k-mooney: ^15:04
bauzaswe need it for the RC115:05
gibidone15:05
bauzasthanks15:05
sean-k-mooneyhehe i was about to say looks like gibi already has15:05
bauzaslet's wait then for both https://review.opendev.org/c/openstack/nova/+/832292 and https://review.opendev.org/c/openstack/nova/+/828570 be merged15:05
bauzaselodilles: ^15:05
bauzaselodilles: once both are merged, we could modify the RC1 nova change 15:05
bauzasand then we'll be done :)15:06
dansmithchateaulav: did you ever float a patch to run the emulation job less?15:10
elodillesbauzas: ack :]15:16
chateaulavdansmith: no, i can15:22
dansmithchateaulav: cool, thanks15:48
opendevreviewArtom Lifshitz proposed openstack/nova master: Explicitly set OS_DEBUG=0 when running default logging test  https://review.opendev.org/c/openstack/nova/+/83311515:54
opendevreviewMerged openstack/nova master: Clean up when queued live migration aborted  https://review.opendev.org/c/openstack/nova/+/82857016:07
opendevreviewMerged openstack/nova master: Add the Yoga prelude section  https://review.opendev.org/c/openstack/nova/+/83229216:07
gibiwe are done \o/ :D16:08
*** gmann is now known as gmann_afk16:13
sean-k-mooney:)16:14
bauzascool16:15
*** gmann_afk is now known as gmann16:29
opendevreviewribaudr proposed openstack/nova master: Fix unit tests when they are run we OS_DEBUG=True  https://review.opendev.org/c/openstack/nova/+/83311516:33
elodillesbauzas: should we wait for something else, or may I update the nova RC1 patch?16:47
bauzaselodilles: I was about to do it but I'm in some brainstrorming internal meeting that tramples my brain16:47
bauzaselodilles: so, shoot16:47
elodillesbauzas: no problem, doing it in a sec! o/16:48
bauzasSHA1 to use : 60094e663c30fd11bb0b1c6923de9e5056adf8be16:48
bauzaselodilles: ^16:48
elodillesyepp, added that16:50
elodillesbauzas: there you go: https://review.opendev.org/c/openstack/releases/+/83241216:50
chateaulavdansmith: just for clarification, after removing from check do i place it under experimental, or is there somewhere else to define it as a weekly periodic?18:12
sean-k-mooneyyou can put it in experimental or periodic-weekly like we do in placment https://github.com/openstack/placement/blob/master/.zuul.yaml#L64-L7318:13
chateaulavsean-k-mooney: thanks18:14
chateaulavok, so then since nova zuul doesnt have periodic weekly specified my patch would be the one to introduce it18:15
sean-k-mooneyyes just add that section and move the job into it18:16
sean-k-mooneythere is also a periodic: pipeline that runs nightly i think but weekly shoudl be enough18:16
sean-k-mooneywe can check the status in the team meeting18:17
chateaulavthanks18:21
opendevreviewJonathan Race proposed openstack/nova master: Changes Emulation CI to weekly-periodic  https://review.opendev.org/c/openstack/nova/+/83316318:25
opendevreviewGhanshyam proposed openstack/nova-specs master: Re-propose server boot on specific hypervisor with new RBAC  https://review.opendev.org/c/openstack/nova-specs/+/83316518:42
erlonsean-k-mooney: bauzas: gibi: hey, Im looking at the test_rollback_pre_live_migration test. I'm really puzzled. I have run 10 times or so, and just now I was able to reproduce it locally. Test is still looping. Running all suite 5 or 6 times also didnt break it. 18:47
erlondo you guys have any ideia on what could cause this kind of bug?18:48
opendevreviewErlon R. Cruz proposed openstack/nova master: DNM: Adds regression test for bug LP#1944619  https://review.opendev.org/c/openstack/nova/+/83316618:54
opendevreviewMerged openstack/placement stable/yoga: Update .gitreview for stable/yoga  https://review.opendev.org/c/openstack/placement/+/83297919:19
opendevreviewMerged openstack/placement stable/yoga: Update TOX_CONSTRAINTS_FILE for stable/yoga  https://review.opendev.org/c/openstack/placement/+/83298119:37
sean-k-mooneyerlon: not initaly no. we have seen this type of bug in the past if the test did not wait for async operation to finish or where we were incorrectly sharing global state 23:08
sean-k-mooneyerlon: but that test did not appear to be doing that23:08
*** dasm is now known as dasm|off23:58

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