16:00:01 #startmeeting nova 16:00:01 Meeting started Tue Oct 12 16:00:01 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:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:01 The meeting name has been set to 'nova' 16:00:10 hola folks 16:00:14 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:00:16 o/ 16:00:58 o/ 16:01:39 o/ 16:01:41 o/ 16:01:50 ok, let's start 16:02:26 #topic Bugs (stuck/critical) 16:02:30 No Critical bug 16:02:36 #link 18 new untriaged bugs (+5 since the last meeting): #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:50 sorry I didn't had to triage the bugs this week, will do that tomorrow 16:03:14 any bug to discuss ? 16:04:00 ok, looks not 16:04:05 #topic Gate status 16:04:09 Nova gate bugs #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure 16:04:19 I saw gibi and sean-k-mooney discussing about one of them 16:04:43 folks, do you want to discuss about this now or off the meeting ? 16:04:55 context : https://bugs.launchpad.net/nova/+bug/1946339 16:04:55 i think off meeting 16:04:59 I have nothing specific to say :) 16:05:06 cool, moving on then 16:05:08 still trying to reproduce / understand what happens 16:05:13 im still reviewing the logs and trying to repoduce 16:05:16 acvk 16:05:24 Placement periodic job status #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly 16:05:42 so you'll see we have a problem with one job 16:05:48 placement-nova-tox-functional-py38 16:07:06 https://zuul.openstack.org/build/055ea1806bf14b1994f1ebdcee720134/log/job-output.txt#808 16:07:10 strange 16:07:14 ubuntu-focal | /bin/sh: 1: Syntax error: "(" unexpected 16:07:19 it looks to me the tox call is wrong 16:07:32 I guess because of the regex 16:07:44 have we modified this ? 16:07:59 /home/zuul/.local/tox/bin/tox --showconfig -efunctional-py38 ^((?!(?:api|notification)_sample_tests|functional\.db\.).)*$ > /tmp/ansible.quewmudg 16:08:06 I'm not waware of any modification recently 16:08:09 I need to take time to look at the regex 16:08:15 to verify whether it works 16:08:49 we touched tox.ini in febr 16:08:57 that was a looong time ago 16:09:11 * bauzas uses https://regex101.com/ 16:09:30 the regex looks valid to me 16:11:38 does not seems like any recent change in openstack-tox-functional-py38 base job too 16:11:49 that has to be something not in tox.init right? 16:12:09 yea 16:12:12 that "get tox envlist config" is some chunk of inlined bash from ansible right/ 16:12:25 yes 16:12:25 https://zuul.openstack.org/build/055ea1806bf14b1994f1ebdcee720134/log/job-output.txt#807 16:12:31 right 16:12:38 that's when calling /home/zuul/.local/tox/bin/tox --showconfig -efunctional-py38 ^((?!(?:api|notification)_sample_tests|functional\.db\.).)*$ > /tmp/ansible.quewmudg 16:12:54 we get a stdout telling "/bin/sh: 1: Syntax error: "(" unexpected" 16:13:02 has anyone just tried runnign the func test locally 16:13:09 yes 16:13:10 not yet 16:13:10 it work for me 16:13:44 that's placement so we can't create a LP bug, but I'd appreciate if we could track in down 16:13:48 track it* down 16:14:35 I'm not used to storyboard honestly 16:15:02 but I guess this is time for me to fly 16:15:11 it is not hard it is just slow :) 16:15:18 very slow :) 16:15:41 and hard :) 16:16:15 well, this is not that's hard, it's just a new foreign language for me to understand :) 16:16:53 * bauzas wonders whether someone will provide a Duolingo feature for Storyboard language 16:17:14 but I can create a "bug" 16:17:19 or you know we could just move it to launchpad 16:17:26 +1 16:17:28 since it now part of the comptue project deliverables 16:17:37 sean-k-mooney: please don't make my dreams tru 16:17:40 true* 16:17:55 honestly, who's looking at the storyboard stories we have for placement ? 16:18:03 I don't :shame: 16:18:06 Balazs Gibizer proposed openstack/placement master: DNM: check tox func job https://review.opendev.org/c/openstack/placement/+/813670 16:18:19 let see if it still fails ^^ 16:18:49 gibi: thanks 16:18:53 gibi: I do not think it will start jobs unless you change any file 16:19:07 I'll create the SB task and let's dissuss this later 16:19:27 that is what we got error from zuul last week 16:19:31 moving on ? 16:19:37 gmann: it seems it is https://zuul.opendev.org/t/openstack/status#813670 16:19:46 bauzas: yes 16:20:10 ah interesting. 16:20:11 k, let's continue 16:20:15 oh, wait then 16:20:29 gmann: we're all listening to you :) 16:20:44 ah, we can move. I will check in parallel 16:21:34 gmann: ok, as you prefer 16:21:37 moving on then 16:21:59 (we can continue to discuss this bug in the open discussion if people want and we have time) 16:22:03 #topic Release Planning 16:22:10 Nova 24.0.0 is now released \o/ 16:22:16 of course, placement too 16:22:30 thanks to all the people who contributed to it 16:23:18 now, we're officially in the Yoga timeframe, even if master is on Yoga since 3 weeks :) 16:23:37 that makes me go to the next deadline 16:23:38 Yoga-1 is due Nova 18th #link https://releases.openstack.org/yoga/schedule.html#y-1 16:25:11 I just wrote something in the PTG agenda about discussing our own deadlines 16:25:30 and whether we should do feature or specs freeze 16:25:39 not wanting to discuss it by now 16:25:46 but start to think about this 16:26:46 we're a bit early in the cycle so a Spec review day is not really important to discuss by now 16:26:57 unless people disagree 16:27:16 we don't have a lot of open specs by now 16:28:20 anyone anything ? 16:28:27 for release planning ? 16:28:49 bauzas: there is two move implemented specs patch https://review.opendev.org/q/project:openstack/nova-specs+status:open 16:29:12 one from you and one from brin 16:29:23 Jan Hartkopf proposed openstack/nova master: docs: add hint to create folder for new microversion https://review.opendev.org/c/openstack/nova/+/813672 16:29:24 oh that's fun 16:29:47 gibi: good catch, will close mine as it's the newest 16:29:59 but I'm not sure brin got all the things 16:30:32 anyway, let's not discuss this now 16:31:40 ack 16:31:50 #topic Review priorities 16:31:56 https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement)+label:Review-Priority%252B1 16:32:38 still continuing to use this flag for tracking changes I wanna review 16:32:57 moving on, we'll discuss the flag usage at the PTG 16:33:01 #topic PTG Planning 16:33:06 every info is in the PTG etherpad #link https://etherpad.opendev.org/p/nova-yoga-ptg 16:33:13 important : 16:33:14 Last week before the PTG, please prepare your points by Thursday EOB so bauzas can provide a nova PTG agenda 16:33:32 (that's an ideal thing) 16:34:02 I'll start moving things around on Friday in order to group related things (if I can) 16:34:22 of course, we'll surely have last minute topics to discuss :) 16:34:30 neutron PTL ( lajoskatona ) seemed interested in some x-p session, we need to find a slot 16:35:21 I just got a email before the meeting from rosmaita about a proposed cinder x-p session slot on Thursday 1pm UTC 16:35:27 wfy ? 16:37:28 works for me, early for the US folks 16:38:31 Balazs Gibizer proposed openstack/nova master: DNM: add traces to troubleshoot bug/1946339 https://review.opendev.org/c/openstack/nova/+/813674 16:38:44 brian is telling that they have 1pm-2.30pm free 16:39:14 so I guess dansmith could join at 1.30pm if he wishes but for melwitt, yeah that could be tough 16:39:32 meaning 1330Z ? 16:39:52 yeah we could start at this time 16:40:02 the two things he had to discuss was : 16:40:07 yeah that's the absolute earliest for me without a special arrangement, 16:40:07 https://blueprints.launchpad.net/cinder/+spec/add-volume-re-image-api 16:40:12 https://blueprints.launchpad.net/nova/+spec/volume-backed-server-rebuild 16:40:13 but not sure I need to be there specifically 16:40:47 ah 16:40:49 I'll try to see if we can get some later slot 16:41:04 melwitt could be interested in one of the two topics 16:41:10 well, like I say, I'll be available at that time, but.. ack 16:41:10 if not the two :) 16:41:20 melwitt: around ? 16:42:11 dansmith: ack, we'll see how this goes 16:42:18 the problem here is that I think both specs are pretty large 16:42:55 they're actually tied 16:43:31 ok, let's move on from this topic, time is flying but I'll see what we can do 16:43:50 the fact is, we'll be missing lyarwood and I'd appreciate if some other volume experts to be there 16:44:42 moving on 16:44:48 #topic Stable Branches 16:44:56 elodilles: floor is yours 16:45:20 let me copy from the meeting page :) 16:45:49 old stable gates are blocked (stein and older), needs the setuptools pinning patch to unblock: https://review.opendev.org/q/I26b2a14e0b91c0ab77299c3e4fbed5f7916fe8cf 16:46:05 Wallaby (23.1.0), Victoria (22.3.0), Ussuri (21.2.3) were released last week 16:46:19 Ussuri Extended Maintenance transition is in a month (Nov 12) - do we want to prepare another release? -- https://etherpad.opendev.org/p/nova-stable-ussuri-em 16:46:55 that was it 16:47:33 since we just released from stable/ussuri I don't know whether we need another release before the transition 16:47:54 but if anyone see any patch that would be good to release then let us know 16:47:58 do we have backports to look at ? 16:48:31 we have lots of backports on ussuri 16:48:42 they are listed on the pad: https://etherpad.opendev.org/p/nova-stable-ussuri-em 16:48:54 yeah I can see them 16:48:55 https://review.opendev.org/q/project:openstack/nova+branch:stable/ussuri+is:open 16:49:16 humpf 16:49:19 I went through the patches and commented on the etherpad for some 16:49:39 I guess one last release would be appreciated 16:49:48 before we call it EM 16:49:49 there are some that needs a second +2 only 16:50:05 elodilles: we can make some kind of status updates at the meetings 16:50:23 bauzas: sure, I'll prepare with that 16:50:28 elodilles: and ping me and a few other stable cores to look at ussuri this week and the week after PTG 16:50:41 ack 16:50:55 #topic Sub/related team Highlights 16:51:01 Libvirt (lyarwood) 16:51:08 lyarwood is not there, nothing to mention 16:51:22 let's move straight to the last bit of the agenda 16:51:25 #topic Open discussion 16:51:29 Next week meeting to be cancelled (PTG). AgreedĀ ? 16:51:36 agre 16:51:37 e 16:51:52 anyone disagreeing ? 16:51:56 1.. 16:51:56 2.. 16:52:00 3.. 16:52:13 OK, that's it, will send the email 16:52:32 I'm done with the agenda now, anyone wanting to raise anything ? 16:52:45 we have 8 mins in the balance :) 16:53:08 just circle back to the placement functional failure 16:53:16 wfm 16:53:17 it still visible on master 16:53:22 gmann: you had thoughts ? 16:53:29 and I do belive this causing https://opendev.org/zuul/zuul-jobs/commit/c02c28a982da8d5a9e7b4ca38d30967f6cd1531d 16:53:34 I think this is because of https://opendev.org/zuul/zuul-jobs/commit/c02c28a982da8d5a9e7b4ca38d30967f6cd1531d 16:53:35 that we include the regexp to the call 16:53:41 gibi: ah you are fast 16:53:59 we simply not need the regexp in that call 16:54:03 or we need to quote it 16:54:30 but I don't know how to feed this back to zuul 16:54:49 gmann: :) 16:55:12 I think bext way is not to include the test regex in tox_extra_args and instead add it as part of command itself 16:55:15 best 16:55:34 let me try that 16:56:14 gmann: ack, we can even left out the regexp param that is not needed for the --showconfig call I think 16:56:35 gmann: gibi: thanks for the findings 16:56:46 I have nothing else for today 16:56:46 yeah, tox_extra_args purpose is completely separate then test regex 16:56:52 gmann: ack 16:57:09 we normally do that with posargs like this https://github.com/openstack/placement/blob/master/tox.ini#L40 16:57:21 yeah 16:57:40 then invoke tox like "tox -e fucntional -- " 16:59:04 i think we can likely close the meeting there 16:59:14 yeah I was about to say 16:59:20 we can continue off meeting 16:59:36 let me call it done 16:59:40 #endmeeting