Tuesday, 2021-09-28

gmannI am checking with sync mode also in case async tasks are creating issue here00:00
gmannand some logging for list all endpoints though endpoints seems fine in this case but will be helpful for other issues https://review.opendev.org/c/openstack/devstack/+/81124600:01
sean-k-mooney[m]melwitt if i remember correctly its pulled in by cloud-init00:15
sean-k-mooney[m]just uninstall python-simplejson00:15
sean-k-mooney[m]you have had to do that on fedora in the past and python-yaml too form time to time00:16
gmannseeing same error with async disable too 01:01
gibigood morning06:35
gibiI see you had a busy day while I was asleep06:36
*** ianw is now known as ianw_pto07:21
bauzasgood morning Nova07:32
gibibauzas: o/07:32
bauzasyeah I saw this07:33
bauzasI'm glad Ian found the root cause07:33
gibiyepp07:35
opendevreviewMerged openstack/nova master: tools: Ignore bot-generated branch creation patches  https://review.opendev.org/c/openstack/nova/+/81028509:27
gibibauzas: I broke the old qos min bw support in Xena when I extended it with qos min pps support: https://bugs.launchpad.net/nova/+bug/1945310 So this bug is probably a Xena regression, but I will only be certain that it wasn't broken after I backported the repro tests to wallaby to see if the fault is not there10:09
bauzasah zut10:09
gibiI have the fixs locally so I think we can still fit this in RC210:11
gibibut we have a broken gate so maybe not10:12
bauzasyep, I dunno what to say10:12
bauzasgibi: maybe we should accept the RC2 proposal for the moment and see whether the fix could be merged tomorrow for providing a RC310:13
gibibauzas: good point10:13
gibithat is the safest bet I think10:13
bauzasgibi: add a comment for our meeting 10:13
gibiso lets talk about this on the meeting today, accept the RC2 if nobody against it and I can push for RC310:13
bauzasyep10:13
gibiadding it to the meeting..10:14
gibidone10:15
bauzasgibi: adding the xena-rc-potential tag to your bug report10:17
bauzascan you triage it ?10:18
gibiack, there is a slight chance that it was similarly broken before xena too hence my hesitation in that10:18
gibiI will triage it10:19
lyarwooddo we not have a bug for the Apache/Placement issue at the moment?10:24
gibilyarwood: I don't see any10:25
gibilyarwood: I only see the fix https://review.opendev.org/c/openstack/devstack/+/81130310:25
lyarwoodyeah same was just checking I hadn't missed something10:26
gibipartial fix, as grenade still needs love10:26
lyarwoodyeah I can't test that until the devstack fix lands10:26
gibilyarwood: I guess this is not even a placement bug but a devstack one10:26
lyarwoodactually I'll just pull both in10:26
gibilyarwood: wait, there are two grenade issues10:26
lyarwoodoh wait sorry I see what you mean re grenade, we need it fixed on both branches10:26
gibilyarwood: in the https://review.opendev.org/c/openstack/devstack/+/811303 grenade still fails with the placement issue10:26
lyarwoodthe devstack issue10:26
lyarwoodright10:27
lyarwoodyeah so we need to land on stable/xena first 10:27
lyarwoodthen master10:27
lyarwoodgood old grenade10:27
gibilyarwood: that was my guess but I wasn't sure10:27
gibilyarwood: so grenade used the devstack from the stable branch?10:27
lyarwoodgibi: yup I believe so10:28
gibinice10:28
elodillesyes, grenade issues usually have to be fixed first at the oldest branch (where the problem exists) and merge "backward"10:30
elodillesis this such an issue?10:30
lyarwoodyeah I think so if it's blocking nova-status checks during the initial install10:31
lyarwoodI guess it needs to go back as far as that apache update landed10:31
elodilles:S10:32
gibiand the apache update is in focal10:32
gibiso it effect all our focal grenade jobs?10:32
lyarwoodit could, I'm just watching the stable/xena job install stable/wallaby now10:33
lyarwoodhttps://zuul.opendev.org/t/openstack/stream/540dea35d7a84633bb00d706fe02136d?logfile=console.log10:33
elodillesif it is only related to focal then we need to fix it first on victoria afaik10:33
elodilles(victoria is the first branch based on focal)10:34
lyarwoodyeah it failed10:37
lyarwoodfun times10:37
gibilyarwood: could you drop a mail to the ML thread about this fun finding?10:38
lyarwoodsure10:38
* lyarwood finds the thread10:38
gibithanks10:41
gibihttp://lists.openstack.org/pipermail/openstack-discuss/2021-September/025101.html10:42
opendevreviewBalazs Gibizer proposed openstack/nova master: Reproduce bug 1945310  https://review.opendev.org/c/openstack/nova/+/81139410:59
opendevreviewBalazs Gibizer proposed openstack/nova master: Query ports with admin client to get resource_request  https://review.opendev.org/c/openstack/nova/+/81139611:00
lyarwoodgibi: I'm going to hold off posting to the thread, I think people are likely aware of the stable requirement here11:07
lyarwoodgibi: but I'm slightly confused by the way forward, it seems that people want to add the trailing / but that's breaking keystone at least on stable/xena11:07
gibilyarwood: ohh, I haven't checked the stable/xena result yet11:13
*** bhagyashris_ is now known as bhagyashris|rover11:16
gibilyarwood: do you think a non trailing / version would pass? 11:17
lyarwoodgibi: it passed on master for the non-grenade jobs11:17
gibihm, true11:17
gibiso then we have to go back and reason about the non trailing / case11:18
lyarwoodyup I think so11:24
opendevreviewBalazs Gibizer proposed openstack/nova master: Query ports with admin client to get resource_request  https://review.opendev.org/c/openstack/nova/+/81139612:13
opendevreviewBalazs Gibizer proposed openstack/nova stable/xena: Reproduce bug 1945310  https://review.opendev.org/c/openstack/nova/+/81140512:19
opendevreviewBalazs Gibizer proposed openstack/nova stable/xena: Query ports with admin client to get resource_request  https://review.opendev.org/c/openstack/nova/+/81140712:21
gibibauzas: now I can confirm that https://bugs.launchpad.net/nova/+bug/1945310 is not fully a xena regression, at least parts of it is reproducible in wallaby too12:28
bauzasgibi: ack, then remove the xena regression tag12:29
bauzasgibi: can you backport the reproduction change to stable/wallaby so the CI would test it ?12:29
gibiI'm doing it right now12:30
bauzascool12:30
bauzasso we don't need a RC3 for it12:30
gibithis is how I confirmed that it is a probelm in wallaby too12:30
bauzasbut we will merge it for a 25.0.1 release 12:30
bauzashuh12:30
bauzas24.0.1 12:30
gibi:)12:30
bauzasgibi: thanks for working on it, very appreciated12:31
gibiI broke it :D12:31
gibiso hell yeah I have to work on it12:31
jamesdenton_altAny ideas as to why Nova might return duplicates for hypervisors and services (same UUIDs)? https://paste.opendev.org/show/809646/12:47
*** jamesdenton_alt is now known as jamesdenton12:47
opendevreviewIvan Kolodyazhny proposed openstack/nova master: Fix NVMe volume attach  https://review.opendev.org/c/openstack/nova/+/81141313:16
opendevreviewBalazs Gibizer proposed openstack/nova stable/wallaby: Reproduce bug 1945310  https://review.opendev.org/c/openstack/nova/+/81141413:20
gibibauzas: so on stable/wallaby we have 2/3 of the bug exists ^^13:21
opendevreviewBalazs Gibizer proposed openstack/nova stable/wallaby: Query ports with admin client to get resource_request  https://review.opendev.org/c/openstack/nova/+/81141613:21
bauzasgibi: over the phone for a meeting but ack13:22
gibime too13:22
opendevreviewIvan Kolodyazhny proposed openstack/nova master: Fix NVMe volume attach  https://review.opendev.org/c/openstack/nova/+/81141313:24
opendevreviewBalazs Gibizer proposed openstack/nova stable/wallaby: Query ports with admin client to get resource_request  https://review.opendev.org/c/openstack/nova/+/81141613:31
*** liuyulong__ is now known as liuyulong13:57
zigoLooks like nova-api on Xena (over Debian Bullseye) doesn't like me...13:58
zigo# openstack server delete 26ee7dd9-75c2-41f5-86f4-c714ed36aab713:58
zigoFailed to delete allocations for consumer 26ee7dd9-75c2-41f5-86f4-c714ed36aab7. Error: {"errors": [{"status": 500, "title": "Internal Server Error", "detail": "The server has either erred or is incapable of performing the requested operation.\n\n unsupported callable  ", "request_id": "req-34a9215b-9387-43b0-ae24-2d85c7d2b8f5"}]} (HTTP 409) (Request-ID: req-57d65ddf-f845-4fa4-9f13-4382ec19dc72)13:58
zigoWhen doing so, nova-api just spams its log with some policy deprecation stuff...13:58
zigoHow am I supposed to generate the default policy file?!?13:59
zigoThis looks like completely broken AGAIN... :(13:59
* bauzas needs to disappear for getting his car from the garage14:00
zigoAlso, has the /healthcheck changed behavior?!?14:01
zigoNow it wants me to be authenticated ?!?14:02
zigoSeriously?14:02
zigoHow am I supposed to do that with the standard haproxy thingy?14:03
bauzasafaik we haven't changed the paste.ini14:03
bauzasthe whole policy thing is different14:03
bauzasbut i need to go away or I'll be pedestrian 14:04
zigoWhen I do a: curl -k https://<hostname>:8774/v2.1/healthcheck  it's now telling me (in json) that I need to be authenticated ... :/14:05
opendevreviewIvan Kolodyazhny proposed openstack/nova master: Fix NVMe volume attach  https://review.opendev.org/c/openstack/nova/+/81141314:05
zigoI'm not even sure that can be done with haproxy.14:05
zigoIt looks like its probably my bad, checking ...14:08
gibilyarwood: does this ring a bell to you https://review.opendev.org/c/openstack/devstack/+/811399/1#message-941958791253e3555a648888281a5de6cbf3b1c4 ?14:08
lyarwoodgibi: nope never seen that before14:12
lyarwoodhttp://review.opendev.org/ dead for everyone?14:12
gibiworks for me14:14
kashyapYeah, same here14:14
dansmithsame14:14
kashyap(As in, works)14:14
dansmithbauzas: is there a tentative ptg schedule yet?14:15
gibidansmith: we have two cross project discussions scheduled to a certain slot but top of that we haven't assigned topics to slots yet 14:17
gibihttps://etherpad.opendev.org/p/nova-yoga-ptg14:17
gibilyarwood: ack, then I recheck :)14:18
dansmithgibi: okay, it's always that arms race where everyone is trying to avoid others' sessions, but nobody has scheduled yet :)14:18
gibiI think it is also part of not having the PTG planning in focus until after Xena is out of the tood14:24
gibidoor14:24
zigoWhen trying to delete a server that went into error, I get this in placement.log:14:24
zigohttps://paste.opendev.org/show/809649/14:24
zigoAny idea why?14:24
dansmithI dunno, I think the "I don't want to schedule X until I know of person Y is available, but person Y's schedule depends on other project Z" problem would exist either way14:25
gibidansmith: true14:26
gibizigo: interesting14:26
zigoMaybe I should try downgrading to oslo.policy 3.7.0 to see what's going on?14:26
dansmiththat error can come from the json encoder/decoder, maybe there's something wrong with the policy file?14:26
zigodansmith: What I'm surprised of, is that I'm using a yaml policy file in /etc/placement/policy.d/00_default_policy.yaml14:27
dansmithzigo: ah, good, that was going to be my next question14:27
zigoAnd there, everything was supposed to be commented out, but it's not: every DEPRECATED stuff is active ...14:27
zigoSame for Nova.14:28
zigo(I had to comment out everything...)14:28
zigodansmith: So you can rule out a policy.json thingy, as I don't have one ! :)14:28
* dansmith nods14:28
zigoSame result with oslo.policy 3.7.014:30
zigoOk, got it to work ...14:33
zigoAgain, same stuff: oslopolicy-sample-generator is generating a default policy yaml file that DOES NOT WORK !14:33
zigoWhen commenting everything out, it works...14:33
gmannzigo:  I do not think oslopolicy-sample-generator add the deprecated rules14:34
zigogmann: That's what it did for me ...14:34
gmannzigo: best way is  not to have policy file if no rule overridden is needed14:34
zigogmann: Well, in my package, I'm writing a /etc/placement/policy.d/00_default_policy.yaml with the expectation that this fille will only contain commented out directives ...14:35
zigoIt worked this way for the last 2 or 3 releases.14:35
zigoNow that's broken.14:35
gmannzigo: commented out you mean except deprecated rules right?14:36
zigogmann: Why would there be some special cases for the deprecated rules?14:36
gmannzigo: no, I mean everything was commented out ? because earlier you mentioned deprecated rules were not commented?14:37
zigogmann: That's what I mean yes, in my packages, now, I have everything commented out but all what's deprecated ... :/14:38
gmann I feel we should extend these tool oslopolicy-sample-generator and oslopolicy-policy-generator to add deprecated rule too with flag so that it does not break deployment not moved to new policies yet14:39
zigoAnyway, GOT MY FIRST Xena VM UP AND RUNNING AND PINGING !!! \o/14:40
gmannzigo: can you paste your old (failing) policy file?14:40
gibi\o/14:40
gmannzigo: perfect14:40
bauzasdansmith: I saw gibi answered you, not for the moment14:40
dansmithack14:40
*** liuyulong_ is now known as liuyulong14:46
gmannzigo: and that policy file (failing ) one is not generated from oslopolicy-sample-generator tool right? is it old one of wallaby or something? 14:47
bauzasdansmith: gibi: that said, I'll try to create an agenda for next week's meeting14:48
bauzascreate a *PTG tentative agenda 14:48
gibibauzas: sounds good let me know if you need help14:49
bauzasgibi: will copy/think/paste :p14:49
gmanngibi: bauzas I added one more cross project topic oslo-nova about this ^^ policy file stuff L56 for now14:49
bauzasack14:49
gibibauzas: I can definitely help with the first and last step, not sure about the middle :P14:49
gmannthis keep coming in every cycle especially when new policy are implemented, I feel we can find some better solution 14:50
gmannzigo: FYI, in case you attend ptg, I have added this topic in PTG discussion. we will discuss if oslopolicy-sample-generator tool can be extended in  way that it works for both deployment with old tokens + new tokens14:52
zigogmann: I've put the files over here: http://shade.infomaniak.ch/policy-files/14:53
zigoI wonder, should I add a sed in all my packages when generating the policy files then?14:53
zigoAs in, commenting-out everything that not commented?14:53
gmannzigo: yeah or can you skip generating it (no policy file) ? I think you need to ship one in packaging ?14:55
zigoWith something like: sed -i 's/^"/#"/ $(CURDIR)/debian/nova-common/etc/nova/policy.d/00_default_policy.yaml14:55
gmannzigo: ok, let me debug that today/tomorrow, having only deprecated rules in policy file should work14:56
zigogmann: I do not *NEED* to generate one, but I think it is a service to the Debian users to provide them with a policy file that has all what's possible...14:56
zigogmann: Well, maybe we should add an option in oslopolicy-sample-generator to comment out the DEPRECATED options ?14:57
zigooslopolicy-sample-generator --commented-out-deprecated-options --output-file=$(CURDIR)/debian/nova-common/etc/nova/policy.d/00_default_policy.yaml --format yaml --namespace nova14:57
gmannzigo: oh does oslopolicy-sample-generator tool generated that file with depreacted rule not commented?14:57
zigogmann: Yeah, that's what I'm saying since the begining ! :)14:58
zigoSorry for not expressing myself correctly ...14:58
gmannhumm14:58
zigoMy package simply does:14:58
zigo        mkdir -p $(CURDIR)/debian/nova-common/etc/nova/policy.d14:58
zigo        PYTHONPATH=$(CURDIR)/debian/tmp/usr/lib/python3/dist-packages oslopolicy-sample-generator \14:58
zigo                --output-file=$(CURDIR)/debian/nova-common/etc/nova/policy.d/00_default_policy.yaml \14:58
zigo                --format yaml \14:58
zigo                --namespace nova14:58
zigoNothing more ...14:58
zigo(note: the PYTHONPATH setting is there to use the installed python3-nova package as if it was in the system)14:59
bauzaslyarwood: seen this ? https://bugs.launchpad.net/nova/+bug/1945323 15:13
bauzasgibi: the reporter proposes ^ for a RC315:13
bauzaswondering whether it's a regression15:14
bauzasbut this sounds valid as it's due to a recent osbrick release15:14
gibibauzas: lyarwood: left a -1 on the fix, but I think his comments confirms that this needs to fixed15:15
bauzasok, so let's do a RC2 for the moment and prepare a RC3 release if so15:16
gibibauzas: based on the gate status we will go with RC2 :D15:17
bauzasgibi: hmmm, because of the pipeline ?15:18
bauzasgibi: I can only see a 2-hour delay which looks a bit busy but still ok-ish15:18
gibibauzas: becuase i) of apache placement break needs to be fixed from victoria to master direction then ii) nova-granade-multinode still need to be fixed with trunk port 15:19
gibijust to enable landing things on master :)15:19
bauzashah15:19
gibian we have 2 days left15:20
bauzasgibi: could we say to not use the latest osbrick release for Xena then ?15:22
gibithat also a patch to the requirements.txt to pin osbrick15:23
gibiwhich we need to land15:23
gibiwe can say in the bug report this as a suggestion15:23
bauzassurely15:23
gibiand packagers can apply it15:23
bauzasI wasn't thinking of our reqs15:23
bauzasbut rather documenting it for packagers15:23
bauzasin reno15:23
gibiyeah reno could work as that does not require full CI run15:24
bauzaswe have a "bugs" reno section AFAICR15:24
gibiyepp you are right, this is a good idea15:24
gibito doc as known bug15:24
bauzaslet's discuss then it during the meeting15:24
bauzasI'll be off for the next 30 mins, I have some appointment coming at home 15:25
bauzasbut I'll be there for the start15:25
bauzasgibi: ^ (fyk)15:25
gibibauzas: ack15:25
zigoHad to do this: https://salsa.debian.org/openstack-team/services/nova/-/commit/7c55fbf4356399f96906162accb3fa80d70f9d2415:26
zigo:/15:26
zigoShould that be reported to oslo.policy?15:26
bauzasgibi: grabbing the bug reports for the gate hold15:27
bauzasgibi: do you have them already somewhere ?15:27
bauzasI wanna write them for the meeting agenda15:27
gibibauzas: we don't have bugreport for devstack about the apache placement break15:27
bauzasI've seen the apache issue in the ML, but I haven't seen a proper bug report yet15:27
bauzasdang15:27
gibibauzas: also we don't have bugreport for the nova-granade-multinode issue either :/15:28
gibi(we are lazy asses)15:28
bauzasmerveilleux15:28
gibibut at leat we are discussing that in #openstack-neutron now in their CI meeting as we suspect they broke that for us15:29
gmannzigo: yes please, file a bug there and I will debug that15:32
lyarwoodbauzas: I wouldn't hold rc for that fix FWIW15:41
zigogmann: https://bugs.launchpad.net/oslo.policy/+bug/194533615:41
* bauzas is back15:46
gibilyarwood: fyi, during the neutron ci meeting we talked about the nova-grenade-multinode issue and slaweq point at https://review.opendev.org/c/openstack/neutron/+/793141 that might be related15:51
lyarwoodkk thanks15:52
gibiit is in xena, and grenade just started using devstack15:52
gibis/devstac/xena devstack/15:52
ralonsohgibi, so far, I've seen three new extensions (between jobs executed 4 days ago and today)15:56
ralonsohqos-pps15:56
ralonsohdns-integration-domain-keywords15:56
ralonsohecmp_routes15:56
bauzasnova meeting in 3 mins15:58
bauzas*here*15:58
gibiralonsoh: ack16:00
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Sep 28 16:00:32 2021 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
bauzashola ! 16:00
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:01
bauzasthanks for being here16:01
bauzaswho's around ?16:01
* stephenfin is lurking16:01
elodilleso/16:01
gibi\o16:02
bauzaslet's start16:02
bauzas#topic Bugs (stuck/critical) 16:02
bauzasNo Critical bug16:03
bauzas#link 13 new untriaged bugs (+0 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New16:03
bauzasthanks for people who triaged them :)16:03
bauzas one open bug marked with xena-rc-potential tag #link https://bugs.launchpad.net/nova/+bugs?field.tag=xena-rc-potential16:03
gibibauzas: was it you ?:)16:03
bauzasgibi: shhhhhhhhtttt :p16:03
bauzasso, https://bugs.launchpad.net/nova/+bug/1945323 is proposed against RC*16:04
gibi:x16:04
bauzastl;dr: last osbrick release is creating problems for NVMe volumes16:04
bauzasthe fix is provided https://review.opendev.org/c/openstack/nova/+/811413 but not yet merged16:05
bauzaswe'll discuss about RC releases in the next topic, but here the question is, should we try to merge ^ before Thursday as it's the deadline for RC16:05
bauzas?16:05
bauzaslyarwood had concerns and I have an opinion16:06
gibiI think if the fix is valid then we should aim to land it16:06
gibibut the gate state might not allow that16:06
bauzasgiven the gate is bad at the moment (again, we will discuss this later), we could try to land it but at least we should provide a releasenotes documentation 16:06
bauzastelling about the bug 16:06
bauzasso, in case we can't land the fix, operators would still see the documentation and for example packagers wouldn't use the latest osbrick if they want to support NVMe16:07
bauzasthoughts ?16:07
bauzasremember that we have a "bugs" section in nova relnotes16:07
bauzas(this gives a "known bugs" section)16:07
gibiI agree to land a reno, regardless of the fix16:08
bauzasgiven I proposed, I need to write it16:08
bauzasbut someone could write it if they want :)16:08
bauzase0ne: around ?16:09
bauzaswe're discussing about your open bug https://bugs.launchpad.net/nova/+bug/194532316:09
e0nebauzas: hi16:09
bauzasand we're proposing you to write a reno change documenting the known bug16:09
bauzasso in case we can't merge the fix before thursday's deadline for RCs, operators would have a documentation explaining how to workaround 16:10
e0neok16:10
e0nefair enough16:10
bauzase0ne: can you write it ?16:10
e0neI understand that we found it too late16:10
bauzasI wish you would be better than me explaining the issue and how to workaround for an ops16:10
e0nebauzas: ok, will do it a bit later today16:10
bauzase0ne: the problem is not really about the time, this is more about the gate block we have atm16:11
lyarwoodsorry back16:11
gmann on gate url issue  - I think we need to go with no trailing '/' in both place but we need to push changes on stable branches first to make grenade job work. basically in reverse order. I will try after an hr or so, currently in another meeting.16:11
bauzaslyarwood: you had concerns on this bug, btw. take the mic16:11
bauzasgmann: we'll discuss the gate problems litterally after this one :)16:12
gmannk16:12
lyarwoodbauzas: I don't even think it's a valid nova bug at the moment, it doesn't look like os-brick has actually changed it's return value with that fix16:12
lyarwoodbauzas: and even if it had that's on os-brick not nova16:12
bauzasdo we have a reproduction test ?16:12
lyarwoodtbh this just smells like a poorly tested codepath16:12
bauzase0ne: ^16:12
e0nelyarwood: there was an issue with CI. it's fixed now16:13
bauzase0ne: you mean that CI wasn't using the latest osbrick hence not seeing the issue ?16:13
e0nemellanox CI should fail with this issue on os-brick patches now16:13
bauzasack16:14
bauzasfwiw, gibi also has another bugfix he wants to merge that's not a regression, so I guess we will provide a Xena stable release like 2 weeks after GA16:14
e0nebauzas: when I merged that patch I was confused by mellanox CI Cinder-tgtadm16:15
lyarwoodyup either way I don't think this needs to land in rc16:15
gibibauzas: yupp this is a 1/3 xena regression and 2/3 existing bug in wallaby https://bugs.launchpad.net/nova/+bug/194531016:15
gibibauzas: and I'm fine to include it in 24.0.1 later16:15
bauzasok, then let's do this16:16
e0nelyarwood: ok, I totally understand you. thanks for letting me discuss it16:16
bauzase0ne: ping me when you're done with the reno patch16:16
e0nebauzas: ok, will do16:16
bauzase0ne: use the 'bugs' section for it please16:16
bauzascool16:16
bauzasand for the fix itself, let's review it sooner than later in master16:17
bauzasso we could backport it to stable/xena as quickly as we can16:17
bauzaslyarwood: do you had time to review the fix itself ?16:17
lyarwoodI already have several times16:18
bauzasnice16:18
bauzasso we need a second core volunteering for reviewing it :)16:18
lyarwoodhttps://review.opendev.org/c/openstack/os-brick/+/800014/7/os_brick/initiator/connectors/nvmeof.py#199 and FWIW I think this is a regression in os-briclk16:18
bauzashah16:18
bauzasso, no nova impact ?16:18
e0nelyarwood: I'll discuss it in cinder meeting tomorrow too16:19
bauzasok, then let's clarify the solution later16:19
bauzasthe reno doc is the priority, the fix itself needs a bit more care I guess16:19
bauzasmoving on16:19
bauzas #topic Gate status 16:19
bauzas Nova gate bugs #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure16:19
bauzaswe triaged a few other ones16:19
bauzasbut, 16:20
bauzas CI is blocked due to nova-grenade-multinode issue and apache placement issue16:20
bauzasgmann: your turn16:20
gmannfrickler: ianw_pto figured it out on apache2 security bugs, you might have seen in email16:20
gmannwe have two option 1. no trailing '/' 2. having trailing '/' in both url and target16:21
gmannlater one seems causing keystone error so we might need to go with first one16:21
bauzasgrabbing the link for the sake of understanding16:21
gibithat is the current fix proposal #link https://review.opendev.org/c/openstack/devstack/+/81139916:21
bauzas#link http://lists.openstack.org/pipermail/openstack-discuss/2021-September/025101.html16:21
gmannbut we need to do it on stable branches first due to grenade jobs , I will try to push changes in stable in reverse order and see if it all work till master. 16:22
bauzastl:dr: apache config is swallowing the placement endpoint URL16:22
gmannso in summary it may take time, hope today we get fixes in16:22
gmanngibi: yeah and ceph things on victoria is another thing16:23
gibigmann: the stable/victoria fix failing with ceph issue now https://review.opendev.org/c/openstack/devstack/+/81139916:23
bauzasgmann: any pointer for the nova-grenade-multinode issue ?16:23
gibigmann: yepp, it is not relataed but it is blocking16:23
gmanntrue16:23
bauzasgmann: can't see any bug for either the apache issue or the grenade thing16:23
gmannbauzas:  nova-grenade-multinode  you mean for neutron-truck extension right?16:23
bauzasthis is correct16:23
gibigmann: right16:23
gmannyeah, I have lyarwood patch in list. let's get this apache things in then I will take a look into that16:24
lyarwoodhttps://review.opendev.org/c/openstack/grenade/+/811117 is the fix for that16:24
lyarwoodI can create a bug16:24
gibiyepp we need to fix the apache first anyhow16:24
gmannyeah ^^16:24
gmannlyarwood: that will be good to track, please file 16:24
bauzas#link https://review.opendev.org/c/openstack/grenade/+/81111716:25
bauzasgmann: if you can do the same for the devstack bug, it would be appreciated16:25
gmannbauzas: sure, we have not logged yet :). will do16:25
gmannlyarwood:  is nova-grenade-multinode  breaking in stable too? 16:25
lyarwoodYeah everything with focal16:26
lyarwoodoh wait16:26
bauzas\o/16:26
lyarwoodI'm mixing things16:26
gmannwe did extension cap in devstack stable/ but need to check if we have neutron-truck in the list there or no16:26
lyarwoodno AFAICT that's just stable/xena to master I think 16:26
gmannlyarwood: ok, stable/xena is not capped with extension yet 16:27
bauzaswe definitely need bug reports to understand the impact :)16:27
gibiI also think wallaby is not affecte by the trunk testing problem in grenade16:27
bauzasstable/xena is the top priority I'd say16:27
lyarwoodgmann: would you have a link to the cap on stable/wallaby?16:27
gmanngibi: ok, need to check if that extension is enbaled or not may be we are just skipping it :) but I will check 16:27
bauzaswe can delay stable releases 16:28
bauzasbut we can't delay Xena GA16:28
gmannlyarwood: https://github.com/openstack/devstack/blob/stable/wallaby/lib/tempest#L669-L68516:28
gmann#link https://github.com/openstack/devstack/blob/stable/wallaby/lib/tempest#L669-L68516:28
gibibut we have to fix stable grenade first to fix master to have GA :D16:28
bauzasyeah, tangled.16:28
bauzasand this is not a Disney.16:28
bauzasanyway, I guess we can move on ?16:29
gibiwith this apache update just now Murphy hit us hard16:29
bauzaswith this last words from gibi full of hope, I guess we can move on16:29
bauzas:D16:29
gmannI will try to push extensions cap in xena too but anyways we have to get apache fix in first16:30
bauzas Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly16:30
bauzas Please look at the gate failures, file a bug, and add an  elastic-recheck signature in the opendev/elastic-recheck repo (example:  #link https://review.opendev.org/#/c/759967)16:30
bauzas #topic Release Planning 16:30
bauzas Release tracking etherpad #link https://etherpad.opendev.org/p/nova-xena-rc-potential16:30
bauzasRC2 proposals are up for approval #link https://review.opendev.org/c/openstack/releases/+/811092 and https://review.opendev.org/c/openstack/releases/+/81109416:31
bauzas Remember to propose regression bugfixes for a new RC with nova-xena-rc-potential16:31
bauzas Final RC to be proposed before end of Thursday Oct 1st (only if needed)16:31
bauzas (gibi): Potential Xena regression #link https://bugs.launchpad.net/nova/+bug/194531016:31
gibiyepp16:31
gibias I said about16:31
bauzasgibi: the floor is yours16:31
gibiit is 1/3 xena regression 2/3 bug in wallaby16:31
gibifix is proposed 16:31
gibiboth on master, xena, wallaby16:32
gibibut I'm OK to delay this until 24.0.116:32
bauzasfor this 1/3, and given the gate, can we assume we'll deliver the fix only as a stable release patch ?16:32
bauzasok, sold16:32
gibiyepp16:32
bauzasI'll approve the RC2 patches tonight then16:32
lyarwoodhttps://bugs.launchpad.net/grenade/+bug/1945346 for the neutron-trunk issue16:32
gibiit only affect min bw + live migration + non-admin token16:32
bauzasuntil someone has strong objections16:32
bauzaswe *can* deliver a RC3 tomorrow or thursday if needed16:33
gibibauzas: I'm OK to land RC2 both for nova and placement now16:33
bauzaskeeping in mind we're in a bad shape for it tho16:33
bauzasbut, crossed fingers16:33
bauzasgibi: ack, will tell the release folks we're good to go for the current proposals16:33
bauzas #topic Review priorities 16:33
elodilles(bauzas: ack :))16:33
bauzashttps://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement)+label:Review-Priority%252B116:34
bauzasI've used a bit this rp label16:34
bauzasI'll try to do reviews for the ones I've taken before end of this week16:34
*** artom_ is now known as artom16:35
bauzasif someone btw. has patches to review, please ping me on IRC so I can mark them with the Review-Priority flag16:35
bauzasalso, avoid CC'ing nova-core in gerrit, this is useless16:35
artombauzas, since you asked https://review.opendev.org/c/openstack/nova/+/808474/3 :)16:36
bauzas(until we discuss about what to do with this tag at the PTG)16:36
bauzasartom: your wish come true16:37
bauzas #topic PTG Planning 16:37
bauzas every info is in the PTG etherpad #link https://etherpad.opendev.org/p/nova-yoga-ptg16:37
artomWait, we're in the meeting, are we?16:37
artomSorry, completely out of it16:37
bauzas If you see a need for a specific cross project section then please let me know16:37
bauzasartom: you're a terrible coworker16:38
artomI'm a terrible human being in general, but that's besides the point ;)16:38
bauzasfwiw, I can start to write up a proposed PTG agenda as a tentative next week16:38
bauzasat least we need to sync up with the oslo team about when to have a cross-project discussion for the policy thing (/cc gmann)16:39
bauzas #topic Stable Branches 16:40
bauzas nova's stable/ussuri and stable/train are blocked (due to latest virtualenv uses latest setuptools which removed use_2to3) 16:40
bauzas(last but not the least large topic)16:40
bauzas large discussion occurred on the ML #link http://lists.openstack.org/pipermail/openstack-discuss/2021-September/024987.html16:40
bauzas looks a consensus is going forward with pinning virtualenv on stable branches # link https://review.opendev.org/c/openstack/nova/+/810461 16:40
bauzastbc, we WON'T pin virtualenv (and setuptools) on master16:40
bauzasbut we WILL pin virtualenv (and setuptools accordingly) on the required stable branches16:41
bauzasanyone disagreeing with this plan ?16:41
gibi(as a side note this only pins setuptools if you use tox, if you install the package by other means the this solution doesn't help)16:42
bauzasgibi: you're the mastermind of this plan, you could add things if you wish16:42
bauzasgibi: excellent detail indeed16:42
bauzasthe pin is only done on tox.ini16:42
gibicurrently we have issue with lower-constraints and tox, so it helps us16:42
gibibut on the ML there was other reports where devstack install failed on stable16:42
bauzaspackagers are free to pick any dependency they want, for sure16:42
gibiso in the long run we might need additional fix for devstack too16:43
bauzasgibi: you mean, we should pin virtualenv in stable devstack releases ?16:43
bauzas(which makes sense)16:44
gibibauzas: potentially yes. I haven't see such failure myself yet16:44
gibiso I'm not rushing with it16:44
bauzasinteresting16:44
bauzasany distro impacted so far ?16:44
bauzas(for devstack)16:44
gibiI have no details16:44
bauzasawesome16:44
elodillesas I understood devstack is not hit with this issue in general (but I might be wrong)16:44
bauzasand I guess no bug report16:44
bauzaselodilles: what I guess is that it depends on the related OS16:45
elodillesbauzas: that sounds possible16:45
bauzasthen, the one who claims there is a bug should explain which env they use16:45
bauzasso we could reproduce it16:46
bauzasfor the moment, let's not try to boil the ocean16:46
gibibauzas: as I said I saw reports on ML but I did not see it in nova yet, so probably the devstack part is not a nova issue right now16:46
bauzasgibi: ok, so let's move on with the tox change16:47
gibiack16:47
bauzasbut again, we'll probably hit the other gate issues16:47
bauzasanyway16:47
bauzasthis release sounds so fun16:47
bauzasmoving on16:47
bauzas #topic Stable Branches 16:47
bauzaswhoops16:48
bauzasplacement branches are also impacted16:48
bauzas we waited with the wallaby release until xena RC2 gets released,  now we could release from victoria and ussuri together with wallaby as  well16:48
elodillesi can prepare the release patches for victoria and ussuri if needed16:48
bauzaselodilles: I guess we'll need some kind of smart stitching between all the concurrent patches so we can unblock things one after all16:49
bauzaselodilles: sure, let's discuss this tomorrow16:49
elodillesbauzas: ack16:50
bauzasother points on stable to discuss ?16:50
elodillesbauzas: actually, i'll be on pto tomorrow, but be back on thursday16:50
elodillesbut anyway, nothing else from me :X16:50
bauzaselodilles: ok, then ping me on thursday so we can arrange a quick wrap-up about what to release and what's missing16:50
bauzas #topic Sub/related team Highlights 16:50
elodillesbauzas: ++16:50
bauzas Libvirt (bauzas)16:50
bauzasnothing to tell honestly16:51
bauzasbtw. I will change the libvirt chairing to lyarwood for next week16:52
bauzasapologies, i forgot to modify it 16:52
bauzaslyarwood: anything worth mentioning about libvirt ?16:52
lyarwoodnot yet :)16:53
bauzashold your patchrds16:53
bauzaspatches*16:53
bauzas #topic Open discussion 16:53
gansoo/16:53
bauzas (bauzas) : Call for Outreachy mentoring extended until Sep 29 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-September/024992.html16:53
bauzaswe have an opportunity for mentoring here16:53
bauzaswe haven't brainstormed about the potential projects we could propose to outreachy students16:54
bauzasbut I'm sure we have room for them16:54
bauzasif anyone has any idea, shoot 16:54
bauzasI can propose to mentor16:54
gibiDear student please fix the CI before GA, thanks. :P16:54
gmann:)16:55
bauzaslol16:55
bauzasI've noticed a bit late tho16:55
bauzasanyway16:56
gibido we have ongoing work where easy to join?16:56
gibimypy maybe ;)16:56
bauzasgibi: I was about to say functional testing but yeah16:57
gansohi! sorry I wanted to ask this before the meeting ended. 2 weeks ago it was mentioned in this meeting that there would be a new tag release soon for all stable branches. Is there any more specific estimate on when the new tag release will happen?16:57
gibibauzas: do we still have osc novaclient gaps?16:57
bauzasgibi: I guess so16:57
gibibauzas: that would be also a good proposal16:57
gibibauzas: or simply filling the osc gaps for placement, we have missed a list of microversions there16:57
bauzasinteresting idea16:58
bauzasone alterative I had in mind was to see how to use some mdev testing framework for validating our GPUs in our CI16:58
bauzasbut anyway, ganso has a question and we're 1 min 16:59
bauzasganso: we just discussed we're considering to tag stable releases end of this week if we can 16:59
gansogreat!16:59
gansothanks!16:59
bauzas*if we can* as we have some blockers that need help17:00
bauzasbut we're overtime17:00
bauzasthanks all17:00
bauzas#endmeeting17:00
opendevmeetMeeting ended Tue Sep 28 17:00:25 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2021/nova.2021-09-28-16.00.html17:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2021/nova.2021-09-28-16.00.txt17:00
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2021/nova.2021-09-28-16.00.log.html17:00
gibigmann: do you say that we need something like https://github.com/openstack/devstack/blob/stable/wallaby/lib/tempest#L669-L685 to stable/xena in devstack to fix nova-grenade-multinode?17:01
gibilyarwood: ^^17:01
opendevreviewIvan Kolodyazhny proposed openstack/nova master: Add release note which descrube NVMe attach issue  https://review.opendev.org/c/openstack/nova/+/81144717:01
gmanngibi: yes but I saw neutron-truck extension is not enabled there so checking if that is correct or wrong17:01
gibigmann: this change sets NETWORK_API_EXTENSIONS which we saw missing in the failing grenade jobs17:02
gibigmann: as far as I see we never enabled trunk in grenade before17:02
gibigmann: but we can try17:02
gmanngibi: yeah, as you mentioned in review, master is with 'all' which means everything is enabled 17:02
gibigmann: OK, thanks for pointing out the solution. We chased this for a day without success. 17:04
gmanngibi: I should have done that while capping the microversion in stable/xena but just late by one day and then apache thing came up17:05
gibigmann: I guess this capping is logically part of the devstack xena branch cut and the grenade switch from testing wallaby ->  master to testing xena -> master17:05
gibigmann: I see. 17:06
gibigmann: I should remember this17:06
gmannyeah, its just all these should go into sequence. I have added all of these stuff in QA release wiki but let me add it with depends-on things so that we avoid any issue in future17:07
gibigmann: could you paste the link to that wiki, I want to learn more :)17:09
gmanngibi: this one https://wiki.openstack.org/wiki/QA/releases17:09
gibithanks17:09
gmannlyarwood: can you remove WIP from https://review.opendev.org/c/openstack/grenade/+/81111717:20
lyarwoodgmann: I can if you don't want to fix this by capping things in tempest?17:21
lyarwoodI haven't had a positive test run with this yet because of the other issues as well btw17:21
gmannlyarwood: capping is skipping the tests which is what happening in stable/wallaby so not broken :)17:21
gmannlyarwood: ok, let me enable this extension in stable/wallaby|xena and then we can test it with your fix17:22
*** slaweq_ is now known as slaweq17:22
lyarwoodgmann: right but we should be skipping if the extension isn't installed right?17:22
lyarwoodgmann: oh sorry tempest is hardcoded to assume these things are available17:23
gmannlyarwood: right but we do enable service in tempest multinode job17:23
gmannso basically grenade also should17:23
gmannyeah17:23
lyarwoodright the issue is that grenade isn't derived from that17:23
lyarwoodyeah17:23
lyarwoodokay17:23
lyarwoodlet me remove the WIP now17:23
admin1hi all ..suddenly nova-compute is connecting and disconnecting to rabbitmq ..  OSError: Server unexpectedly closed connection   .. and then reconnected ....    in all 3 rabbitmq containers, netstat shows around 2000 connected sockets in each .. is this something that others have also seen ? 19:30
admin1did i hit a bug at rabbitmq 19:30
*** amodi_ is now known as amodi19:50
*** elodilles is now known as elodilles_pto20:52
gouthamrhello seeing a devstack failure in some of the manila jobs; the "nova-status upgrade check" in devstack's post tasks fails the Placement API check... Details: Placement API does not seem to be running.21:27
gouthamrthese jobs don't disable placement, and the placement-api logs don't show anything abnormal; example: https://zuul.opendev.org/t/openstack/build/727954069097463495e9e9d774101278/log/controller/logs/screen-placement-api.txt21:28
toskygouthamr: there is an email iirc21:28
toskygouthamr: isn't it http://lists.openstack.org/pipermail/openstack-discuss/2021-September/025101.html ? 21:29
gouthamrah! it is! 21:29
gouthamrthanks tosky!21:29
clarkbthe fixes are all in the gate right now21:30
clarkbwe have to roll them forward from victoria to master due to grenade21:30
gouthamrgreat, thank you clarkb (/me watches https://review.opendev.org/c/openstack/devstack/+/811399 and the train)21:32
gmanngouthamr: as you are here, nova ceph jobs also broken which need fix in devstack-plugin-ceph. https://review.opendev.org/q/I7061f8d1491ff957452c9c777e40186a4e9c324e22:22
gmannI am still testing it on victoria and wallaby22:23
gouthamrack, saw your change gmann 22:23
gmanngouthamr: ok, I might need your help to merge it after testing22:23
gouthamrthanks for the patch! yep :) i'm on it22:23
gmannthanks22:24
opendevreviewGhanshyam proposed openstack/nova stable/wallaby: DNM: Testing nova-grenade-multinode with neutron-trunk  https://review.opendev.org/c/openstack/nova/+/81151323:20
opendevreviewGhanshyam proposed openstack/nova stable/xena: DNM: Testing nova-grenade-multinode with neutron-trunk  https://review.opendev.org/c/openstack/nova/+/81149123:22

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