16:00:15 #startmeeting nova 16:00:15 Meeting started Thu Sep 3 16:00:15 2020 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:19 The meeting name has been set to 'nova' 16:00:51 o/ 16:00:58 o/ 16:01:01 o7 16:01:58 lets get started 16:01:59 #topic Bugs (stuck/critical) 16:02:02 No critical 16:02:09 #link 29 new untriaged bugs (-2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:28 as the release is closing I hope we can all focus a bit more on bug triage 16:02:29 o/ 16:02:43 Is there any open bug that needs special attention? 16:03:09 * bauzas waves late 16:03:27 o/ 16:03:47 gibi: the focal detach volume bug could use more attention I think 16:03:48 if no bugs then 16:03:55 lyarwood: yeah 16:04:02 gibi: but we could cover that in the libvirt section later 16:04:06 lyarwood, wait, is that related to https://review.opendev.org/#/c/742014/5? 16:04:25 no, lets try to get some volunteer to look at that bug 16:04:36 (We're hitting an issue in whitebox where if we use focal we can't attach volumes) 16:04:40 I mean no, don't wait for the libvirt section :D 16:04:51 https://bugs.launchpad.net/nova/+bug/1882521 16:04:53 Launchpad bug 1882521 in OpenStack Compute (nova) "Failing device detachments on Focal" [High,New] 16:04:56 artom: no the issues we've seen has been on detach ^ 16:05:06 artom: but I can look at yours as well 16:05:16 * stephenfin wanders in even later 16:05:19 gibi: FWIW I'm looking at this but I've yet to find anything of value tbh 16:05:35 lyarwood, I need to look at it anyways, I can analyze and report back 16:05:40 Good to know it might be a known thing 16:05:47 artom: any help is appreciated 16:05:57 I'll also ask kashyap 16:06:07 i saw it hitting on designate testing also but no checked if that is exactly same or someting new 16:07:59 I promised in the past to look at it but failed to reach that point in my queue 16:08:03 so I won't promise again 16:08:09 kk I think we can move on 16:08:12 OK 16:08:17 any other bugs? 16:08:31 lyarwood, weirdly, I can't find that volume UUID anywhere in the logs :P 16:08:44 #topic Runways 16:08:50 etherpad #link https://etherpad.opendev.org/p/nova-runways-victoria 16:08:57 emoved bp/cyborg-rebuild-and-evacuate as the slot expired and the main implementation is merged, some follow up patches are still open 16:09:03 *removed 16:09:22 the patches for bp/add-emulated-virtual-tpm are approved and moving through the gate 16:09:31 othing is in the queue but I think this is actually a good thing considering that next week is feature freeze 16:09:36 *nothing 16:09:40 * gibi fails at copy pasting 16:10:40 bauzas, you had a thing we wanted to get in, no? I guess it means it's not making it? 16:10:56 I have a patch I'm working on 16:11:01 for the routed networks series 16:11:04 but it's a bit late 16:11:12 if I can provide it tomorrow, people can review 16:11:13 we will see next week 16:11:19 or tomorrow :) 16:11:22 or we will punt it, meh 16:11:34 I also have the sriov attach 75% done 16:11:46 (I finally found a solution for passing the requested networks :) ) 16:11:48 but I can also accept if it will miss the release 16:11:52 bauzas: \o/ 16:12:32 is there any other feature that is still open but close to being finished? 16:13:16 I take the silence as now 16:13:18 I take the silence as no 16:13:25 #topic Release Planning 16:13:29 next weeks is Milestone 3 which is Feature Freeze 16:13:42 release tracking etherpad #link https://etherpad.opendev.org/p/nova-victoria-rc-potential 16:13:48 This week is the non client library freeze, os-vif release patch is up #link https://review.opendev.org/#/c/749535/ 16:14:25 I will talk to sean-k-mooney before I approve it 16:14:42 Next week is client library freeze 16:14:44 I don't see any open patches on python-novaclient #link https://review.opendev.org/#/q/project:openstack/python-novaclient+status:open+branch:master 16:15:07 is there any novaclient change that we need before the release? 16:15:36 there aren't any microversion changes to nova so nothing mandatory anyway 16:16:10 OK, cool 16:16:33 I wrote up the Cycle Highlights #link https://review.opendev.org/#/c/749693/ please review it 16:17:24 ack will do 16:17:38 It's already merged? 16:17:39 and last but not least 16:17:53 wao 16:17:56 it is merged 16:18:00 Sean (McGinnis) was quick on the trigger :P 16:18:06 now worries 16:18:23 just leave your comment on the merged review and I will do a follow up patch 16:19:50 so last but not least we need a volunteer to write the release notes prelude for Victoria 16:21:06 I will ask again next week :) 16:21:12 I don't mind, but do we have past examples? And I don't feel like I've been around enough to know wtf is up :/ 16:21:16 I can do the prelude 16:21:25 Sold! /me retracts himself 16:21:28 Actually, if artom wants to nvm 16:21:34 jinx, no u! 16:22:01 You write. I'll critique mercilessly? 16:22:09 Ussuri prelude patch https://review.opendev.org/#/c/721548/ 16:22:13 Wouldn't have it any other way 16:22:31 (Wait, why did I accept that? I lose on every count) 16:22:35 gibi: I can do 16:22:46 (sorry I was a bit afk) 16:22:51 ah whoops 16:23:20 stephenfin, I legit have the problem of not knowing what happened well enough, though 16:23:23 ok so one of the 3 volenters can submit a patch 16:23:29 yes, please :) 16:23:29 and the rest of us can review it 16:23:33 sure 16:23:55 remember, the timeline is important, we need to merge it before RC1 16:24:11 or people will kill us with anger 16:24:12 I will make sure you won't forget about that 16:24:34 the who is who ? 16:24:38 me or stephenfin? 16:24:51 I don't bother, I wrote a couple of preludes already 16:24:59 bauzas: you 16:25:02 haha 16:25:20 would hate to break the tradition 16:25:24 :) 16:25:30 OK then it is sold to bauzas 16:25:33 :D 16:25:47 I won't argue. 16:25:51 Is there any other release related issue? 16:26:32 #topic Stable Branches 16:26:41 lyarwood, elod: any news? 16:27:12 only that we are waiting for https://review.opendev.org/#/c/747360/ to land before cutting a stein release AFAIK 16:27:24 any other +W needed for stable changes ? 16:27:26 ussuri and train already done thanks to elod 16:27:28 I thought not 16:27:37 ack good :) 16:27:38 nothing from my side. setuptools released 50.1 ~15hrs ago, that solves the issues with stable branches 16:27:51 thanks 16:27:55 #topic Sub/related team Highlights 16:27:59 API (gmann) 16:28:17 update on json to yaml policy file migration 16:28:45 oslo side work is merged and released, i will update the nova patch by today - https://review.opendev.org/#/q/topic:bp/policy-json-to-yaml+(status:open+OR+status:merged) 16:29:06 i am testing that locally and should be up by an hour or so 16:30:14 i think we can make it in m-3 release. 16:30:26 let's hope so 16:30:35 thanks 16:30:50 anything else on the api side? 16:31:15 other thing is stephenfin patch which i replied on gerrit. 16:31:31 Yeah, I was suggesting we find some work to do on the API to justify a microversion 16:31:49 lol 16:31:51 please don't blow up the API one week before the FF :) 16:31:58 or jsut add a microversion that has no chagne to signal the removal 16:32:01 Purely to make my life easier for the XenAPI deprecation 16:32:01 i think it is good sign if no microverison in any release :) 16:32:18 sean-k-mooney: we did it in the past 16:32:18 stephenfin: :) 16:32:38 i assumed we might but i could not recal when 16:32:40 but as gmann sensibly noted that would require a spec, and I'm not sure it's worth the effort 16:33:01 then we remove xenapi early next cycle 16:33:03 stephenfin: is there an alternative to the bump? 16:33:13 Yeah, a config option in Tempest 16:33:15 like 6 weeks form now 16:33:19 stephenfin: yeah, i think we can just remove those TODO as changing those status codes is not actually worth 16:33:30 sean-k-mooney: that assumes there will be microversion bump in the next release 16:33:45 gibi: yeah we can do via config option which is how tempest handle the release wise featrure testing 16:33:51 feature 16:34:00 OK, that seems like a good alternative 16:34:29 anything else on the api side? 16:34:43 that's all from me 16:34:46 thanks 16:34:47 actually I was wrong 16:35:08 we never used a microversion just for signaling, since we also provided 404s for nova-network 16:35:21 Libvirt (bauzas) 16:35:21 so, hands on, folks, please 16:35:27 well, 16:35:33 #link https://etherpad.opendev.org/p/nova-libvirt-subteam 16:35:37 is pretty empty 16:35:48 yeah I need to add https://review.opendev.org/#/q/topic:bump-libvirt-qemu-victoria there 16:35:51 so, in case folks beg for reviews, please amend ^ 16:36:08 which is looks like it is also blocked by https://bugs.launchpad.net/nova/+bug/1882521 16:36:09 Launchpad bug 1882521 in OpenStack Compute (nova) "Failing device detachments on Focal" [High,New] 16:36:14 even though this is bionic 16:36:22 but with updated qemu and libvirt versions 16:36:22 lyarwood: Is that okay to merge now, yeah? You got the Ubuntu issue resolved? 16:36:25 Ah 16:36:43 and it's getting really late in the cycle to land something like this tbh 16:36:51 stephenfin: the issue would affeect centos8 and rhel too 16:37:06 we should switch 16:37:10 sean-k-mooney: it should but I can't reproduce on either bionic, focal or f32 16:37:19 https://opendev.org/openstack/governance/src/branch/master/reference/runtimes/victoria.rst 16:37:22 on any of them even 16:37:48 per the govnace resolution the offial supported distro version for ubuntu is 20.04 for victoria 16:38:08 kk so this is a blocker to the release then? 16:38:13 https://bugs.launchpad.net/nova/+bug/1882521 that is 16:38:14 Launchpad bug 1882521 in OpenStack Compute (nova) "Failing device detachments on Focal" [High,New] 16:38:29 it sure sounds like it 16:38:35 phun 16:38:35 yup 16:38:39 so im not sure it always happens 16:38:55 (that from someone that's been mostly disengaged from the effort to date, admittedly) 16:39:01 but its is showing up in the gate periodicly 16:39:09 these failing tests are skipped for now in Focal base job migration patches. 16:39:28 gmann: I really don't think they should be tbh 16:39:29 we can test it via unskipping those but they were failing all the time 16:39:30 ok so we shoudl be able to swap the gate jobs over 16:39:52 releasing V with this still happening would be wrong tbh 16:40:13 lyarwood: yeah i mean just to continue the testing we did skip those test but for completing the migration we should not unskip 16:40:26 should unskip 16:40:30 gmann: is there a central change I can depend on to switch to focal btw? 16:40:33 ok so it look liek we have to fix this before the release so 16:40:44 gmann: I'll just drop the bionic UCA stuff and focus on focal 16:40:59 o/ 16:41:07 about libvirt-subteam : I will take care of this one because it just popup on my infra : https://bugs.launchpad.net/nova/+bug/1795747 16:41:08 Launchpad bug 1795747 in OpenStack Compute (nova) "libvirtError: unsupported configuration: Found duplicate drive address for disk with target name 'sda' controller='0' bus='0' target='0' unit='0' when try to create an instance with two scsi volumes" [Undecided,New] - Assigned to Arthur Dayne (palagend) 16:41:50 lyarwood: you can add DNM oatch on top of this and by unskipping those tests https://review.opendev.org/#/c/734700/ 16:41:55 DNM patch 16:42:29 OK, please continue troubleshooting the focal bug, but lets move on here 16:42:33 aarents: i tought we fixed that already 16:42:40 gmann: ack thanks 16:42:53 moving on ? 16:42:57 sean-k-mooney: good news 16:43:02 #topic PTG and Forum planning 16:43:08 The next Forum and PTG is less than 2 months from now 16:43:19 aarents: we might not have but we change how we enumarte thing to fix a similar issue. 16:43:20 please indicate your acceptable PTG timeslots in #link https://doodle.com/poll/a5pgqh7bypq8piew before 7th of September 16:43:38 PTG etherped #link #link https://etherpad.opendev.org/p/nova-wallaby-ptg 16:44:21 at the moment there are not much topic there 16:44:28 so I cannot judge how much time we need 16:44:34 or if we need cross project session or not 16:44:44 so please start populating the PTG pad 16:44:57 anything else related to the PTG? 16:45:41 #topic Open discussion 16:45:47 there is one thing on the agenda 16:45:58 "Can we support return the reserved_memory and reserved_cpu info when call the list-hypervisors-details api ?" 16:46:19 but there is no nick attached so I don't know who added it 16:46:27 did we always say go check placemtn for that 16:46:32 can i change the question ? 16:46:42 "can we deprecate the os-hypervisors API ?" 16:46:53 this ^ 16:46:55 well yes that was the resoning for using placement 16:47:05 we wanted to delete that api 16:47:22 I agree, this is returned from placement already 16:47:28 stephenfin: man, you're the king of code cleanups, just fire a change 16:48:06 bauzas: I' not 100% sure everything in the os-hypervisor is in placement now 16:48:19 then we need to spec it 16:48:31 well we need a spec in either case 16:48:33 I can write it for Wallaby 16:48:35 all api changes do 16:48:49 yeah 16:49:00 sean-k-mooney: I know, but... :D 16:49:04 OK, I think we are in agreement here 16:49:09 any other open discussion topic? 16:49:19 sean-k-mooney: technically, we don't need a microversion for *deprecating* an API 16:50:18 bauzas: right but we do need a spec to remove it or make any user visable changes 16:50:19 * bauzas adds a TODO for him : write an os-hypervisors API deprecation spc 16:50:33 sean-k-mooney: right, but I only said "deprecate" 16:51:00 if nothing else for today then I will let you 10 minutes go early ;) 16:51:05 9 16:51:15 we could have been deprecating the API without a spec and then discuss on a spec (or at the PTG) the next actions for signal or feature parity 16:51:27 gibi: my mouth will love it 16:51:34 thirsty it is 16:51:35 bauzas: suggest to add a topic to the PTG etherpad ^^ 16:51:40 OK 16:51:43 yeah ! 3 topics now ! 16:51:48 let's finish this 16:51:50 :) 16:51:55 thank you all for joining 16:51:58 #endmeeting