Earlier  
Posted Nick Remark
#openstack-nova - 2020-09-15
09:09:33 yingjisun I only see 68 "Starting instance ..." in the log.
09:09:45 bauzas lyarwood: because we have something called "Feature Freeze"
09:09:58 bauzas even with low risk deprecations
09:10:10 bauzas that's maybe me who is a bit conservative
09:10:12 stephenfin yingjisun: https://docs.openstack.org/nova/latest/admin/vendordata.html
09:10:18 bauzas but is it really a thing ?
09:10:26 stephenfin yingjisun: The vendordata feature provides a way to pass vendor or deployment-specific information to instances. This can be accessed by users using the metadata service or with config drives.
09:10:28 lyarwood sorry I don't see how feature freeze is even related to deprecations
09:10:40 bauzas lyarwood: you're possibly right
09:10:45 bauzas I just raise a concern
09:10:55 lyarwood ff is for new things, deprecations are just to highlight removal in a future release
09:10:56 bauzas in theory, RCs are there for focusing on bugds
09:11:13 bauzas but I'm pedantic
09:11:15 lyarwood yeah true I just didn't map deprecations to adding risk
09:11:22 lyarwood removing stuff maybe
09:11:45 lyarwood the only reason I'm still going through stephenfin's xenapi removal stuff is because the bulk has already landed
09:11:53 lyarwood so we are only removing stuff that's dead anyway now
09:12:41 stephenfin yingjisun: I suspect you have either something like cloud-init on the guests indexing the metadata service
09:12:48 stephenfin s/either //
09:14:03 bauzas stephenfin: that's my expectations
09:14:16 stephenfin lyarwood, bauzas: Yeah, it would be good to discuss as a team whether we want to proceed with that remove-xenapi series and close it out this cycle, or wait until Wallaby
09:14:17 bauzas that's what I explained
09:14:24 stephenfin bauzas: oh, so you did /o\
09:14:29 bauzas it's cloud-init thingies
09:14:30 stephenfin sorry, I missed that
09:14:35 bauzas so litterally a guest question
09:14:38 stephenfin yuuup
09:14:48 lyarwood stephenfin: yeah I'd like to remove the already dead stuff before RC if we can
09:15:05 lyarwood or did I miss rc already being cut
09:15:12 bauzas no
09:15:16 bauzas next week
09:15:23 bauzas and https://review.opendev.org/#/c/751045/1 is -W because of this
09:15:44 bauzas I'd certainly prefer if we would stop merging things that would touch nova features
09:15:52 lyarwood k, if we have a week I'd say push ahead removing dead code but would be good to bring up on Thursday if it's still going on
09:16:10 lyarwood bauzas: FWIW the bulk of the removal has already landed so listing it there is valid now
09:16:21 bauzas lyarwood: this is
09:16:34 bauzas my concern was more about any other deprecation or removal we were about to provide
09:17:06 lyarwood kk what's the deadline for the prelude? after rc?
09:17:32 lyarwood IOW can we just set a deadline of rc for deprecations and respin the prelude?
09:17:44 bauzas lyarwood: no, prelude has to merge before we branch
09:17:52 stephenfin it has to merge before the branch
09:17:54 stephenfin yeah
09:17:58 bauzas but again, the whole point of RCs is to focus on bugfixes
09:18:06 stephenfin otherwise it's not included in the 22.0.0 tag
09:18:12 lyarwood yeah understood
09:18:23 lyarwood but we aren't at rc yet soooooo
09:18:42 lyarwood I'd think deprecations are fine until we land the prelude and branch?
09:18:49 bauzas and us pushing things down the line after FF makes me a bit sad since we all communicate on the glorious ideal of whight knights only caring about bugs for the next 2 weeks
09:19:04 bauzas call me an idealist
09:19:32 lyarwood isn't that post rc?
09:19:37 stephenfin bauzas: personally, I can't imagine us adding anything big enough to warrant inclusion in the prelude so I think that could be fixed up to mention XenAPI/VMWareAPI changes and merged
09:19:40 lyarwood I know we do it between ff and rc as well
09:19:53 lyarwood but rc to ga is critical bugfixes etc as well right?
09:20:34 bauzas lyarwood: no, RCs are intended for bugfixes, including the period between M3 and RC1
09:20:43 stephenfin lyarwood: on an RC-related note, what have we decided on Focal changes for Victoria? Are we simply skipping those tests until the QEMU fix lands in 20.04?
09:20:51 bauzas the period between RC1 and GA being focused on *regressions*
09:21:06 stephenfin yes, I realize I should know this already /o\
09:21:17 lyarwood stephenfin: I think the TC are pushing ahead with the focal change so yeah
09:21:23 bauzas so in the world of OpenStack, in theory you only focus on bugs for only two weeks in a 6-month timeframe \o/
09:21:27 lyarwood stephenfin: loads of jobs don't skip them still
09:25:53 openstackgerrit Sylvain Bauza proposed openstack/nova master: Victoria 22.0.0 prelude section https://review.opendev.org/751045
09:26:23 gibi bauzas, stephenfin, lyarwood: regarding deprecatios post FF, I'm OK to finish up the xenapi removal before RC1 but in general please focus on bug triage instead of proposing new deprecations
09:26:45 bauzas gibi: I'm litterally on it :p
09:27:22 bauzas gibi: no lock held on triage ?
09:28:41 lyarwood stephenfin / sean-k-mooney ; https://zuul.opendev.org/t/openstack/build/11627c525c7a48138fba5d3e4c50c4e9/log/controller/logs/screen-q-dhcp.txt?severity=4 - appreciate this isn't our area but would either of you be able to look at this, I'm trying to finally sort out f32 jobs by the q-dhcp agent isn't happy, any ideas?
09:28:49 lyarwood https://review.opendev.org/#/c/750292/ is the review
09:29:12 lyarwood no idea what's borked here tbh
09:31:03 gibi bauzas: I don't hold the bug lock
09:31:05 gibi go ahead
09:33:27 yingjisun stephenfin: for the feature of Vendordata, is it keep running over and over when the instance is powered on ?
09:36:06 bauzas yingjisun: no, it's not working this way
09:36:24 bauzas yingjisun: it's a metadata API that instances can reach internally
09:36:36 bauzas exactly like the user metadata
09:37:20 bauzas yingjisun: so hitting this API is solely the responsability of apps running on top of the instances
09:37:25 yingjisun so you guess there might be some process inside the instance which keeps to invoke it ?
09:37:46 bauzas yingjisun: that'd be my expectations
09:37:55 bauzas but you can see what hits the API
09:38:03 bauzas so you can track
09:38:13 brinzhang0 stephenfin, gibi: please review this patch, followed-up with cyborg evacuate patch https://review.opendev.org/#/c/749052/
09:39:46 bauzas yingjisun: see this blogpost explaining how metadata API is reached https://www.suse.com/c/vms-get-access-metadata-neutron/
09:40:11 yingjisun bauzas: thank you. I read it now.
09:42:00 bauzas yingjisun: actually, https://docs.openstack.org/nova/latest/admin/metadata-service.html explains it better
09:43:28 bauzas so you can easily get the instance IP address
10:06:55 sean-k-mooney lyarwood i would not be surrpised if the output of the tool neutron is calling has changed
10:07:14 lyarwood sean-k-mooney: I can't seem to reproduce it locally
10:07:26 lyarwood sean-k-mooney: so it might be yet another load thing
10:10:13 lyarwood kashyap: https://bugs.launchpad.net/qemu/+bug/1894804 any news on this btw?
10:10:13 openstack Launchpad bug 1894804 in QEMU "Second DEVICE_DELETED event missing during virtio-blk disk device detach" [Undecided,New]
10:12:04 sean-k-mooney lyarwood: so its failing here https://github.com/openstack/neutron/blob/master/neutron/agent/linux/ip_lib.py#L955-L967
10:13:05 bauzas lyarwood: this one seems legit for Nova https://bugs.launchpad.net/nova/+bug/1892837
10:13:05 openstack Launchpad bug 1892837 in tripleo "tempest.api.compute.servers.test_servers_negative fails in periodic-tripleo-ci-centos-8-standalone-full-tempest-api-master" [Critical,Triaged]
10:13:52 lyarwood bauzas: yup less of a priority with the workaround in Tempest but still a valid Nova bug
10:14:02 bauzas ack, triaged.
10:14:48 lyarwood just cleaning up my untriaged but fix released bugs btw, appears launchpad/gerrit hasn't been keeping up
10:15:35 sean-k-mooney lyarwood: this might be realted to a change that merged recently. i think the if need to be split. it currently prints that message if the device does not exist or if it does not have a mac
10:16:28 sean-k-mooney lyarwood: is it causing the job to fail
10:17:18 sean-k-mooney that would be a yes it is
10:17:20 kashyap lyarwood: No news yet :-( - but I haven't forgotten; Was responding to something more pressing elsewhere
10:17:42 lyarwood sean-k-mooney: yeah AFAICT the instances aren't getting ipv4 dhcp leases and so ssh verification is failing
10:17:50 lyarwood kashyap: ack np just chasing up

Earlier   Later