16:01:01 #startmeeting nova 16:01:01 Meeting started Tue Nov 22 16:01:01 2022 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:01 The meeting name has been set to 'nova' 16:01:06 o/ 16:02:40 sorry folks, forgot we had an internal meeting at the same time 16:02:52 not sure we'll have a lot of folks around 16:03:10 hello o/ 16:03:18 o/ 16:03:30 o/ 16:03:31 ok, let's start then 16:04:01 actually, I forgot to provide my PTG notes for the internal meeting :D 16:04:09 so I won't need to discuss :) 16:04:39 #topic Bugs (stuck/critical) 16:04:45 #info No Critical bug 16:04:49 o/ 16:04:50 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 11 new untriaged bugs (+4 since the last meeting) 16:04:55 #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster 16:05:09 sean-k-mooney: can you use the bug baton for next week ? 16:05:15 Balazs Gibizer proposed openstack/nova stable/train: Reproduce bug 1896463 in func env https://review.opendev.org/c/openstack/nova/+/841288 16:05:16 Balazs Gibizer proposed openstack/nova stable/train: Set instance host and drop migration under lock https://review.opendev.org/c/openstack/nova/+/841444 16:05:35 i guess but its likely the last round i can do this year 16:05:44 all cool 16:07:04 o/ 16:07:05 #info bug baton is being passed to sean-k-mooney 16:07:21 any bug to discuss or do we move on ? 16:07:27 (please say the latter :) ) 16:08:12 k, moving on 16:09:10 #topic Gate status 16:09:16 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:09:21 #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status 16:09:29 huzzah, the periodics are back \o/ 16:09:42 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:09:47 #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures 16:10:02 anything to discuss about gate ? 16:11:43 just a note 16:11:49 sure 16:11:53 the gate should now be jammy/22.04 16:12:09 have we merged the changes ? 16:12:20 the base jobs changed at m1 16:12:21 sorry, was a bit off the IRC channel during those two days 16:12:26 kk 16:12:31 so i belive they merged last week 16:13:01 anywya just keep an eye out and see if there are any new issues 16:13:16 thats all i wanted to raise 16:13:21 https://review.opendev.org/c/openstack/nova/+/861111 16:13:50 so the base jobs seem to have been merged indeed, but not our jobs 16:14:21 actully that patch is keeping one job on focal 16:14:24 gmann: can you help us by explaining what we do atm ? 16:14:36 yes, like 2 years ago 16:14:38 although i woudl argue grenade shoudl be that job 16:14:39 we keep an old job 16:14:51 i dont think we need a new one 16:14:59 and then we run all the other tempest jobs with the latest ubuntu version 16:15:37 yeah so 16:15:38 this cycle the grenade jobs shoudl be on focal which shoudl provide enough test coverage 16:15:45 #link https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/861116 Base jobs are migrated to Jammy 16:16:04 ill comment on the review 16:16:09 #link https://review.opendev.org/c/openstack/nova/+/861111 Nova specific jobs migration to Jammy need to be reviewed 16:16:27 sean-k-mooney: me too 16:16:35 ok, anything else ? 16:16:53 nope 16:16:57 not from me 16:17:05 moving on 16:18:23 #topic Release Planning 16:18:29 #link https://releases.openstack.org/antelope/schedule.html 16:18:34 #info Antelope-1 was last week 16:18:39 #info Spec review day had 6 specs merged and more than 10 others being discussed. 16:18:48 kudos to the reviewers who worked on it 16:19:21 as a reminder, we will get another spec review day in a couple of weeks before milestone-2 16:19:45 we should also plan some implementation review day around between a-1 and a-2 16:20:30 voilĂ , anything to discuss about either the spec review day or antelope-1 ? 16:21:32 fwiw, we merged a release for novaclient https://review.opendev.org/c/openstack/releases/+/861360 16:21:52 and ditto for os-vif https://review.opendev.org/c/openstack/releases/+/864527 16:22:29 if no questions, let's move on 16:26:47 sorry, I'm being dragged in a meeting, can someone continue ? 16:26:49 gibi: ? 16:27:03 sure I will try 16:27:29 #topic Review priorities 16:27:35 #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) 16:27:40 #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review 16:27:54 is there anything we need to discuss on these priorities? 16:28:43 #topic Stable Branches 16:28:52 elodilles: your turn :) 16:29:04 I have a quetion on stable/train 16:29:26 #info wallaby is blocked due to failing nova-ceph-multistore, workaround: https://review.opendev.org/c/openstack/nova/+/865134 16:29:45 this is an interesting one, stable cores, please review if possible ^^^ 16:29:55 #info ussuri and train is blocked due to nova-multi-cell job, possible fix: https://review.opendev.org/c/openstack/tempest/+/865300 16:30:15 ^^^ thanks sean-k-mooney for calling my attention to the issue :) 16:30:26 #info rest of the stable branches should be OK 16:30:33 #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci 16:30:43 i appoved the first one addign os-brick to requried project will also make depends on work 16:30:43 and that's it from my side 16:31:14 elodilles: do you know about any issues on stable/train 16:31:29 ok, I'm back 16:31:30 I see multiple job failing with 16:31:30 sean-k-mooney: thanks. i think that is the most straightforward workaround for the situation 16:31:30 rsync: [sender] link_stat "/var/lib/zuul/builds/eacfbbe59b6a4297a4aebb16cc7d2140/work/ca-bundle.pem" failed: No such file or directory (2) 16:31:33 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3] 16:31:55 ie https://review.opendev.org/c/openstack/nova/+/841444/4 16:32:06 s/ie/eg/ 16:32:34 gibi: rsync problem usually happened due to infra issues, but those usually temporary / intermittent issues 16:33:02 gibi: train is blocked, see above :) 16:33:05 I got it mutliple times. I did a rebase at the start of the meeting if that hits the same I will ping the team again as that will mean it is blocked 16:33:08 #chair gibi 16:33:08 Current chairs: bauzas gibi 16:33:26 (just added gibi for chair, not sure the bot will correctly set the topics) 16:33:35 elodilles: aaah, 16:33:45 sorry it is a bit hard to be on two meetings in parallel 16:33:51 so we know that train is broken 16:33:53 :S 16:33:57 then I have no other question :) 16:34:04 gibi: yepp, but not with the rsync error 16:34:25 so that's a new thing if it is a permanent problem :( 16:34:26 interesting 16:34:28 we should name the train bug "sncf" as train is always broken :) 16:34:42 anyhow I will report back if the same failure happens in the recent rebase too 16:34:58 gibi: ack, thx 16:35:07 I thank you :) 16:35:17 any other topics on stable? 16:35:23 looks not 16:35:57 moving on ? 16:36:01 I'll need to speak in a little 16:36:26 #topic Open discussion 16:36:30 (jsanemet) Improve usage of privsep on Nova: 16:36:31 Bug ticket: https://bugs.launchpad.net/nova/+bug/1996213 Proposal: https://etherpad.opendev.org/p/nova-privsep-review Does the change deserve a spec? 16:36:48 yeah so 16:37:22 jsanemet: on the spec question. Do you feel you have open question that would need upfront decision from the core team? 16:37:25 I discussed with jsanemet about his efforts and I proposed him to present himself and discuss about how we could paper the privsep effort during the meeting 16:37:40 the spec thing was more a wonder we had 16:37:52 I don't honestly feel it requires one spec 16:38:06 but we tho need to consider documenting the new context usages 16:38:12 hence the etherpad 16:38:52 hello 16:38:53 I don't see any upgrade impact, or any other impact which would require us to accept a spedc 16:39:38 anyone disagree with that plan ? 16:40:21 what is the effort? just finishing some things? 16:40:28 or something more complex? 16:40:29 dansmith: https://etherpad.opendev.org/p/nova-privsep-review 16:40:42 dansmith: this is about fine-graining the privsep context to the right callers 16:40:43 there are several 16:40:58 this looks like the first low haning fruit 16:40:59 yeah so splitting into different contexts? 16:41:06 yep 16:41:08 as a first step yes 16:41:21 I dunno, I think that's going to be a bunch of review of which calls need which contexts right? 16:41:31 that's my concern 16:41:35 some things might seem simple but require both net and sys, etc 16:41:35 I don't think we need a spec 16:41:38 but, 16:42:01 I guess I'm not sure why no spec 16:42:03 I'd appreciate if we would agree on the contexts and the callers not exacly by reviewing the patches 16:42:07 this etherpad is half a spec already 16:42:15 there proably should be a spec to define the scope 16:42:21 agree 16:42:27 there, we have our answer 16:42:37 we can use the spec format to agree on the split 16:42:57 sure 16:43:30 jsanemet: you're ok with the outcome ? 16:43:39 I can help you on the process-y thingie 16:44:05 sure 16:44:22 then, i will translate the etherpad into a spec and we can discuss it further 16:44:26 seems good to me 16:44:33 from a paperwork pov, you may also need to supersede the rfe bug by creating a launchpad blueprint 16:44:48 but that's an easy peasy 16:45:01 anyway, looks like we have the direction 16:45:06 yes, i am a little green regarding what documentation is required so any help will be appreciated 16:45:39 jsanemet: as a reminder, you have a spec template https://specs.openstack.org/openstack/nova-specs/specs/2023.1/template.html 16:46:10 I guess that's it for today 16:46:11 all right, i will save that 16:46:15 thanks a lot 16:46:36 ok, folks, any other item to raise before we call the wrap ? 16:46:58 looks not 16:47:01 perfect timing 16:47:05 thanks all 16:47:08 #endmeeting