Thursday, 2023-05-11

dansmithmelwitt: oh jeez I didn't realize that wasn't +V from zuul, thanks00:19
melwittnp. it's hard to see through all the fail00:20
dansmithjust too many patches really00:20
melwitthuh.. it looks like it's already been running. it was already +W by you.. I didn't think of the +W kicking off the job again /facepalm00:23
dansmithoh I swore it was00:23
dansmithI see your recheck put it back in the arm queue,00:24
dansmithwhich is only a few minutes old but the other one has been running in regular check for over an hour00:24
dansmithI thought I must have been looking at the wrong on00:24
melwittyeah. it doesn't restart the normal jobs thankfully00:24
melwittno, I'm just le dumb00:24
dansmithno, there are too many identical patches :)00:25
dansmithcrap, 2023.1 patch is going to fail00:33
dansmithdhcp fail in the guest00:34
dansmithle sigh00:34
melwittdangit00:34
dansmithtop patch is +V waiting for another trip to gateland00:49
dansmithman cripes00:49
dansmithmy friggin timeout patch is gonna fail again00:49
melwitt😑 00:50
dansmithclearly something ceph related:00:50
dansmith[   10.258086] Buffer I/O error on dev vda1, logical block 20, lost async page write00:50
dansmithvda is the root disk, which is on ceph00:50
dansmithlast time around cinder just stopped creating volumes halfway through (maybe for similar reasons)00:51
dansmithOut of memory: Killed process 55722 (ceph-osd)00:52
dansmiththat'll do it like every time00:52
dansmithcripes00:52
melwittouch00:53
dansmithah, 00:54
dansmithwe're lowering the swap on our fatter job than the ceph job I increased in their repo00:54
opendevreviewDan Smith proposed openstack/nova master: Bump nova-ceph-multstore timeout  https://review.opendev.org/c/openstack/nova/+/88289000:56
dansmithmelwitt: ^00:56
melwittI don't understand that sentence 😆 00:59
* melwitt reads the commit message00:59
melwittok nevermind00:59
dansmithwait, in my commit message or00:59
melwittyeah you explained what I didn't understand in your commit message01:00
dansmithI bumped the ceph job to 8G while jammifiying and cephadmifying it, but we inherit from that and set it down to 4G, which makes no sense because we run even more stuff than they do01:00
dansmithack01:00
*** dmellado9 is now known as dmellado05:04
opendevreviewMerged openstack/nova stable/2023.1: Use force=True for os-brick disconnect during delete  https://review.opendev.org/c/openstack/nova/+/88285805:41
opendevreviewAmit Uniyal proposed openstack/nova stable/2023.1: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/88291305:47
opendevreviewAmit Uniyal proposed openstack/nova stable/zed: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/88291405:50
gibirechecked  https://review.opendev.org/c/openstack/nova/+/882890 as it failed nova-next in the gate with unrealted timeouts 06:43
gibialso rechecked https://review.opendev.org/c/openstack/nova/+/88285906:46
gibiboth failed with http read timeout on various openstack APIs (cinder, neutron, nova)06:47
gibiI think this is tracked here as a bug https://bugs.launchpad.net/tempest/+bug/199989306:48
bauzasmorning07:05
bauzasgibi: catching up the world explosion after my yesterday PTO07:05
gibiI don't have the full context as the CVE got public why I was away07:29
gibiI see the fixes proposed so I'm trying to land them07:29
opendevreviewAmit Uniyal proposed openstack/nova stable/yoga: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/88292007:29
gibis/why/while/07:32
opendevreviewSylvain Bauza proposed openstack/nova stable/2023.1: Revert "Debug Nova APIs call failures"  https://review.opendev.org/c/openstack/nova/+/88278307:32
bauzasgibi: np, just looking at gerrit reviews07:33
bauzasgibi: do you need some explanations ?07:33
gibiI read the CVE it is well documented so thanks I'm OK about the fixes we are pushing07:33
opendevreviewAmit Uniyal proposed openstack/nova stable/xena: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/88292107:34
*** atmark is now known as Guest110707:51
sean-k-mooneybauzas: can you take a look at some os-vif changes for me09:47
sean-k-mooneythis one is trivial https://review.opendev.org/c/openstack/os-vif/+/882755 and this one is the one i really want to merge https://review.opendev.org/c/openstack/os-vif/+/88175109:48
sean-k-mooneyor gibi  or anyone else who is about09:48
bauzassean-k-mooney: fyk see my comment on https://review.opendev.org/c/openstack/os-vif/+/88275510:11
bauzasthe TC will add back py38 in the Bobcat PTI10:12
bauzas(but that's just a FYK, since Focal won't be accepted again)10:12
sean-k-mooney38 i htink is still tested in os-vif10:25
sean-k-mooneyi havent got around to updating that so cool i can leave that10:25
sean-k-mooneywe just use openstack-python3-jobs to contol that10:26
sean-k-mooneyi might add 3.11 like we did in nova seperatly but ill keep 3.8 testable 10:27
sean-k-mooneythanks for the reminder10:27
opendevreviewAmit Uniyal proposed openstack/nova stable/wallaby: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/88293910:32
opendevreviewMerged openstack/nova master: Bump nova-ceph-multstore timeout  https://review.opendev.org/c/openstack/nova/+/88289010:51
gibisean-k-mooney: approved the os-vif qdisc patch12:01
sean-k-mooneygibi: thanks for reviewing 12:02
opendevreviewMerged openstack/os-vif master: remove focal based jobs  https://review.opendev.org/c/openstack/os-vif/+/88275512:08
opendevreviewBalazs Gibizer proposed openstack/nova stable/2023.1: Bump nova-ceph-multstore timeout  https://review.opendev.org/c/openstack/nova/+/88278412:15
bauzasstable cores are needed for 2023.1 https://review.opendev.org/c/openstack/nova/+/88278312:15
gibibauzas, dansmith, melwitt: The nova-ceph-mutlistore timeout bump is merged to master so I cherry-picked it to 2023.1 ^^12:16
bauzasgibi: done12:16
bauzasgibi: sean-k-mooney: could you please look at https://review.opendev.org/c/openstack/nova/+/882783 ?12:16
sean-k-mooneyyep12:17
sean-k-mooneyelodilles: :)12:18
elodillesdone :)12:18
sean-k-mooneybauzas: they are both now +2w'd12:18
gibi\o/12:18
sean-k-mooneyby the way i dont care that w is a letter can cant be past tense but +2w'd is definelty a thing :) and the 'd gets that point across12:20
sean-k-mooneyenglish sometime allows you to convay info in a way that would make tech writers cry12:21
sean-k-mooneyand im ok with that, we all know i mainly comunicate in seanspeak anyway :)12:22
elodillesyepp, i also use EOL'd +2'd +W'd o:)12:22
elodillesi don't remember where i saw that 1st time, but it can be understood, so i started to use that myself too12:25
sean-k-mooneyi dont think any one has ever objected but from a grammer rules point of view english allows you to syntasies past tense verbs this way. i just know my english teach would have been unhappy12:27
sean-k-mooneywith makeing an acronym both be a verb and have tence12:28
sean-k-mooney' is a very powerful thing :)12:28
elodilles:)12:30
Uggla@bauzas, gibi, if you can have a look at those small patches https://review.opendev.org/c/openstack/tempest/+/882822/1, https://review.opendev.org/c/openstack/tempest/+/882823/2 as I said tuesday that may help to find the bug.12:43
ykarelsean-k-mooney, bauzas can you please revisit https://review.opendev.org/c/openstack/nova/+/868419 when get a chance12:54
opendevreviewMerged openstack/nova stable/2023.1: Enable use of service user token with admin context  https://review.opendev.org/c/openstack/nova/+/88285912:56
dansmithgibi: thanks!13:23
opendevreviewAmit Uniyal proposed openstack/nova stable/wallaby: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/88293913:28
bauzasdansmith: thanks btw. for having +2d on my way13:29
bauzasupstream CVE bugfixes are already merged by master and 2023.1 \o/13:30
dansmithbauzas: no problem13:32
opendevreviewMerged openstack/os-vif master: set default qos policy  https://review.opendev.org/c/openstack/os-vif/+/88175113:42
gibiUggla: done. I don't have +2 rights in tempest but those patches looks good13:52
Ugglagibi, cool thx. 13:53
dansmithbauzas: gibi so just an update, based on my opensearch digging, I don't think we have seen any volume detach failures in the last week with the exception of cases where either ceph oomed or the guest had a kernel panic13:56
dansmithnot definitive for sure, but based on previous behavior, I think that's massively better13:56
opendevreviewMerged openstack/nova stable/2023.1: Revert "Debug Nova APIs call failures"  https://review.opendev.org/c/openstack/nova/+/88278314:21
bauzasdansmith: bravo to you14:25
dansmithalso, the cve backport just failed on the backport validator14:25
dansmithmaybe just github not updated yet?14:25
opendevreviewElod Illes proposed openstack/nova master: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88295614:25
elodillesbauzas dansmith : we need this fix as new branch naming broke our validator :S ^^^14:26
dansmithah14:27
dansmith+214:27
elodillesthx 14:27
dansmithelodilles: nice job thanks14:27
elodillesi'll propose the backports if this is about to merge14:28
gibidansmith: nice results!14:28
dansmithcinder is still running with validations disabled and so they're hitting all the ones we used to but we're not, so that's also a nice A/B comparison :)14:29
opendevreviewOleksandr Klymenko proposed openstack/nova master: Host removed from AZ when service is manually disabled  https://review.opendev.org/c/openstack/nova/+/88295714:48
opendevreviewElod Illes proposed openstack/nova stable/2023.1: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296415:05
opendevreviewElod Illes proposed openstack/nova stable/zed: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296515:06
opendevreviewElod Illes proposed openstack/nova stable/yoga: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296615:07
opendevreviewElod Illes proposed openstack/nova stable/xena: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296715:08
opendevreviewElod Illes proposed openstack/nova stable/wallaby: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296815:09
opendevreviewElod Illes proposed openstack/nova stable/victoria: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296915:11
opendevreviewElod Illes proposed openstack/nova stable/ussuri: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88297015:12
opendevreviewElod Illes proposed openstack/nova stable/train: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88297115:13
opendevreviewSylvain Bauza proposed openstack/nova stable/zed: Revert "Debug Nova APIs call failures"  https://review.opendev.org/c/openstack/nova/+/88278615:29
bauzasfolks, I'm also saying it loudly, tomorrow I'll be working and looking at specs16:17
dansmithmelwitt: the backport checker fix is going to fail on functional, that db table race thing16:52
melwittargh16:54
dansmithis there a bug open for that/16:54
melwittyes, sec16:55
dansmithI dunno why zuul hasn't kicked it out so I can recheck it yet16:56
melwittI believe it's this one https://bugs.launchpad.net/nova/+bug/194633916:56
dansmithhmm, similar at least16:57
melwittgibi has done a lot of work to improve the situation but it's a gnarly issue16:57
dansmithokay yeah that's the same16:58
JayFHey; I re-proposed the Ironic sharding spec for this cycle about 2 weeks ago. It's not gotten any reviews. If anyone can take a look I'd appreciate it: https://review.opendev.org/c/openstack/nova-specs/+/88164316:58
melwittthere is a change I think we could do that might help but I haven't proposed it yet bc it hadn't been happening very often for a long time there16:58
dansmithmelwitt: okay gibi just commented on the bug that we've seen an. uptick recently16:59
melwittyeah, I just saw that too16:59
dansmithfungi: there's something that has completed all our jobs in gate that we need to recheck, but it's just sitting there in the queue and I'm not sure why17:12
dansmithit's already identified as failed and out of the queue, but not.. uh, reporting or whatever17:13
clarkbdansmith: because the changes ahead of it haven't finished17:13
clarkbonly the first thing in the queue can report17:13
clarkbdoing so removes it from the queue and then the next item can be processed17:13
dansmithI thought if nothing in front could have caused the failure on that job it would come out immediately 17:13
clarkbzuul doesn't have that information so can't do that17:14
dansmithhmm, okay17:14
clarkbby putting things in the same queue you are asserting a failure in one may be caused by the other17:14
clarkband zuul is operating on that knowledge17:14
dansmithokay17:14
dansmithbut it already shows it as failed out (meaning the fork in the line) so I thought that was it saying it knows the things behind it no longer depend17:15
clarkbcorrect the things behind it no longer depend on it. But the things ahead of it may be where the actual bug is17:15
clarkbin that case you want to evict the broken stuff ahead and restart the things ehind17:16
dansmithso the green checks behind this are based on skipping it or with it applied?17:16
clarkbthe green checks behind are based on skipping the one that has failed17:16
dansmithI assume with it applied and they'll restart if it decides it was legit to kick it out?17:16
dansmithhmm okay17:16
clarkbthe unknown is the not yet completed jobs ahead of it17:16
dansmithso if it doesn't get kicked out they restart?17:16
fungibut they'll all be tested again from scratch if something else ahead of all of those fails a job17:16
clarkbyou have 5 changes, 6th is a failure, then X behind. Zuul does not know if the failure was caused by the 5 changes at the front so it does not completely evict the 6th until it processes the 5 ahead of it17:17
fungiuntil all changes ahead of the failing change merge successfully, zuul can't be sure that there's something wrong with that change17:17
dansmithit's too bad we can't mark a job as isolated or something, because this is only running nova unit tests, but it's held up as if it has the same dependencies as something with a tempest (which is why the queue needs to be shared)17:18
dansmithobviously not a very common case17:18
dansmithfungi: ack, the fork in the graph makes it look to me like it's already "out" but yeah okay17:19
dansmith"out of consideration" I should say17:19
dansmithbut yeah I guess I thought there was job affinity and not just place-in-the-queue17:20
fungiright, if the failure were due to a change ahead of it in an oslo lib, the bug in that oslo change might fail on some other job which exposed the same bug through some other tests which aren't the nova unit test job17:24
fungiit's all fairly abstract from zuul's perspective17:24
dansmithyeah, probably safer that way I guess, it's just not how I thought it worked17:25
sean-k-mooneyJayF: i think we have just been a bit busy and missed it17:29
sean-k-mooneyJayF: one of the things we agree at the ptg however as not to auto reappove previosly approves specs if there was no code proposed in the previos cycle17:30
sean-k-mooneyJayF: i know you were working on the iroinc side fo that last cyle17:31
JayFsean-k-mooney: that's an interesting case; there was lots of code landed last cycle related to that spec. None in nova though (we had to get the Ironic API released, which we have)17:31
sean-k-mooneyJayF: how is that going17:31
JayFIronic shards API exists, was shipped in Antelope17:31
sean-k-mooneyack17:31
JayFopenstacksdk support for it is landed, unsure if released but it can be if eneded17:31
JayFI'm working on Ironic CLI support for that, which is only really needed once the Nova stuff is released17:32
JayFright now, if that spec doesn't hit a speed bump, we've hit every milestone on time17:32
sean-k-mooneycool17:32
sean-k-mooneyare you planning to work on the nova part this cycle17:32
sean-k-mooneyassuimg its the same as the spec form last cycle17:32
sean-k-mooneyi dont really see any issues with it17:33
sean-k-mooneyas long as there is someone to work on it we can review17:33
JayFI believe John Garbutt is going to be doing most of the heavy lifting, with Julia and I as backup / docs writing17:33
sean-k-mooneyok have they confirmed that since john has been out of active nova dev for a while17:33
JayFI have confirmed that downstream17:34
JayFHe helped us with the design, and wrote the spec last cycle which was approved.17:34
JayFEither way, regardless of which human writes the code, it's our intent to implement the spec as listed. I sure hope John does it; his familiarity will save a lot of time but even if not, this is too important to let it live/die on one persons' shoulders.17:35
sean-k-mooneyack17:35
sean-k-mooneyill try an review it proably monday at this point but if they want to +2 it i can proably +w it assuming its basically the same as last cycle.17:36
sean-k-mooneyi was happy with the desgin previously17:36
sean-k-mooneyand i dont think anythin has maritarly change on the nova side that woudl affect it17:37
JayFI appreciate it. My only urgency in getting the spec merged is I believe there's a deadline in the nova process for things we want to land this cycle, yeah?17:37
sean-k-mooneythere technially is but its milestone too17:37
sean-k-mooney*two17:37
sean-k-mooneyso July 6th17:37
JayFaha, I was worried it was -117:37
JayFsounds good :) thanks Sean!17:38
sean-k-mooneyno we encurage peopel to submit the first draft before m117:38
sean-k-mooneyyou have time17:38
JayFI'm going to use some of that time now to land the ironic cli for shards o/ ty again17:38
sean-k-mooneysince i have it open im going to do a quick pass on it and compre to last release but then i need to swap to somethign else.17:41
sean-k-mooneyJayF: the ironic cli is now a osc plugin yes17:42
sean-k-mooneyor does ironic still have a standalone cli too17:42
JayFsean-k-mooney: yes-ish. We have a plugin for OSC which can also operate independently (e.g. with just Ironic client plugin installed, you can still run `baremetal whatever`)17:42
JayFbut if the primary openstack cli client is installed, `openstack baremetal whatever` works 17:43
sean-k-mooneyoh neat17:43
JayFsingle codebase, same command structure, just prefix for when it's integrated vs no prefix when it's not17:43
JayFthat's also why all the Ironic docs use `baremetal X` instead of `openstack baremetal X` (the non-openstack-namespaced version works universally)17:44
sean-k-mooneywell without i assume the "prefix" is the binary name 17:44
sean-k-mooneyso ironic baremetal X ? vs openstack baremental X17:45
JayFGonna be honest; I've done very little work in the clients. Part of why I'm speaking inexactly is my knowledge is inexact.17:45
JayFNo, it's `openstack baremetal X` or `baremetal X` (no Ironic at any point)17:45
sean-k-mooneyno worries17:45
sean-k-mooneyok so then teh console script entryp oint and the binary on the path is called "baremental" then17:46
JayFhttps://github.com/openstack/python-ironicclient/blob/master/setup.cfg#L25 we have both a binary and the entrypoints setup17:46
sean-k-mooneythhat woudl be yes https://github.com/openstack/python-ironicclient/blob/master/setup.cfg#L2717:46
JayFheh jinx17:46
fungidansmith: melwitt: (or anybody else plugged into ossa-2023-003), do you happen to know if the vulnerability affects iscsi based deployments that don't rely on multipathd? i asked just now in https://launchpad.net/bugs/2004555 because an operator reached out to me directly with the question17:47
dansmithfungi: I just replied and pinged gorka17:47
fungioh, perfect. thanks!17:47
sean-k-mooneyJayF: no worreis just had not seen that done before  but that was what i was expecting17:47
opendevreviewMerged openstack/nova master: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88295620:25
opendevreviewMerged openstack/nova stable/2023.1: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296420:25
dansmithwoot20:26
opendevreviewMerged openstack/nova stable/yoga: Remove deleted projects from flavor access list  https://review.opendev.org/c/openstack/nova/+/88131422:40
opendevreviewMerged openstack/nova stable/zed: Ironic: retry when node not available  https://review.opendev.org/c/openstack/nova/+/86792422:40
opendevreviewMerged openstack/nova stable/zed: CI: fix backport validator for new branch naming  https://review.opendev.org/c/openstack/nova/+/88296522:40
opendevreviewMerged openstack/nova master: doc: Update version info  https://review.opendev.org/c/openstack/nova/+/88061423:34

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