Earlier  
Posted Nick Remark
#openstack-nova - 2020-03-18
10:21:16 openstackgerrit Stephen Finucane proposed openstack/nova master: Bump python-subunit minimum to 1.4.0 https://review.opendev.org/713611
10:21:32 stephenfin gibi: ^
10:22:27 stephenfin Also, if you're in the reviewing mood, these two patches are super trivial and good to go https://review.opendev.org/#/c/704533/1 https://review.opendev.org/#/c/710276/2
10:25:35 lyarwood stephenfin: morning morning, how was your lock-in yesterday?
10:26:10 gibi stephenfin: regarding https://review.opendev.org/#/c/710276/2/tox.ini , those thing that you removed are the default now?
10:26:22 lyarwood stephenfin: Could you hit https://review.opendev.org/#/q/status:open+topic:workaround_native_luksv1 & https://review.opendev.org/#/q/status:open+topic:rbd_block_device today if you have time?
10:26:51 bauzas stephenfin: with thoughts ot Saint Patrick, I gladly drank a beer yesterday night to celebrate his memory
10:46:54 openstackgerrit Merged openstack/os-resource-classes master: setup.cfg: Configure 'python-requires' https://review.opendev.org/704533
11:03:42 lyarwood Random question, trying to force an instance to launch on a given host in a fresh stable/queens devstack env using --availability-zone nova:unassigned-hostname but it's always failing in n-sch somehow (shouldn't it skip the filters?)
11:03:59 lyarwood ^ is there any config updates required to make that work with a default devstack env on stable/queens?
11:08:59 bauzas lyarwood: which exact command do you issue ?
11:09:35 lyarwood openstack server create --image cirros-0.3.5-x86_64-disk --flavor m1.xlarge --block-device-mapping vdb=4776528c-f18c-4750-844d-41cbfaf802ab --availability-zone nova:unassigned-hostname test
11:09:35 bauzas lyarwood: and IIRC, --az <host>:<node>:az
11:09:53 bauzas lemme double-check the API
11:10:05 lyarwood https://docs.openstack.org/nova/queens/admin/availability-zones.html
11:10:10 lyarwood ^ is what I was going off
11:10:17 lyarwood and the customers reproducer downstream
11:10:22 lyarwood that uses az:host
11:10:38 bauzas sec, checking
11:10:44 lyarwood compute_api.parse_availability_zone also uses that
11:11:07 bauzas https://github.com/openstack/nova/blob/master/nova/compute/api.py#L475
11:11:34 bauzas lyarwood: but look
11:12:11 bauzas if you don't provide a tuple of 3 items (az, host, node) but only 2 (az, host) then you need to double ":"
11:12:16 bauzas lyarwood: ^
11:12:31 bauzas https://github.com/openstack/nova/blob/master/nova/compute/api.py#L488
11:12:48 bauzas holy snap
11:12:55 bauzas I'm wrong
11:13:12 lyarwood yeah you only need 1
11:13:17 bauzas "::" is for (az, host
11:13:21 bauzas damn
11:13:24 bauzas (az, node)
11:14:02 bauzas lyarwood: I guess you have nova service-list telling you that you have nova-compute on some random host literrally named 'unassigned-hostname' ?
11:14:52 lyarwood $ openstack compute service list --service nova-compute
11:14:53 lyarwood +----+--------------+---------------------+------+---------+-------+----------------------------+
11:14:55 lyarwood | ID | Binary | Host | Zone | Status | State | Updated At |
11:14:57 lyarwood +----+--------------+---------------------+------+---------+-------+----------------------------+
11:14:59 lyarwood | 2 | nova-compute | unassigned-hostname | nova | enabled | up | 2020-03-18T11:14:39.000000 |
11:15:01 lyarwood +----+--------------+---------------------+------+---------+-------+----------------------------+
11:15:03 lyarwood yeah
11:16:49 lyarwood Mar 18 07:02:06 unassigned-hostname nova-scheduler[3674]: DEBUG nova.scheduler.manager [None req-27d6db0a-3f02-4350-8bab-7cc9f93639d0 admin admin] Got no allocation candidates from the Placement API. This may be a temporary occurrence as compute nodes start up and begin reporting inventory to the Placement service. - ah
11:17:10 lyarwood maybe we are bailing on before we even get to filtering the hosts
11:20:17 lyarwood https://github.com/openstack/nova/blob/78e53bd388a5c2305da5249f1f217923d3fe2aac/nova/scheduler/manager.py#L134-L139 yup that's it
11:20:24 bauzas lyarwood: we don't go with checking the filters if you specify a target like this
11:20:39 lyarwood yeah it's failing before we get anywhere near there
11:20:44 lyarwood I think it's the hostname causing issues
11:20:50 lyarwood I'll unstack, set something valid and try again
11:21:10 bauzas weirdo
11:21:33 lyarwood yup indeed
11:45:03 stephenfin lyarwood: Sorry, meetings. Yup, I'll take a look
11:45:40 stephenfin and my lock was me cooped up at home, figuring out how traefik worked with a single beer
11:48:01 stephenfin gibi: replied on https://review.opendev.org/#/c/710276/
11:48:27 lyarwood stephenfin: my deepest condolences
11:48:31 stephenfin I should have been clearer in the commit message - I'd forgotten half the reason I'd done some of that myself. Can edit it if you'd like
11:49:05 lyarwood bauzas: so I'm still getting no allocation candidates from placement
11:50:56 stephenfin yo, bauzas, can you hit https://review.opendev.org/#/c/710239 please?
11:52:30 lyarwood ah wait I'm being stupid
11:55:15 openstackgerrit Merged openstack/nova master: bug-fix: Reject live migration with vpmem https://review.opendev.org/708110
12:09:01 openstackgerrit Merged openstack/nova master: VMware VMDK detach: get adapter type from instance VM https://review.opendev.org/653738
12:14:58 openstackgerrit Luyao Zhong proposed openstack/nova master: support live migration with vpmems https://review.opendev.org/687856
12:21:21 openstackgerrit Luyao Zhong proposed openstack/nova master: Track orphan instances and error migrations in resource tracker https://review.opendev.org/678451
12:42:21 lyarwood eh when did ubuntu make upgrade and dist-upgrade different?
12:42:51 lyarwood I hit this again https://bugs.launchpad.net/os-vif/+bug/1749972 because virt-builder is just running upgrade when you build with --update
12:42:51 openstack Launchpad bug 1749972 in os-vif "`brctl setageing $bridge 0` fails on Ubuntu 16.04 4.4.0-21-generic" [Undecided,Invalid]
12:43:06 lyarwood *sigh*
12:43:27 sean-k-mooney lyarwood: its always been different
12:43:42 sean-k-mooney lyarwood: dist-upgrade upgrades your kernel and all other packages
12:44:02 sean-k-mooney upgrade will hold back some packages that would require a hots reboot to take effect
12:44:39 lyarwood sean-k-mooney: ack thanks, I haven't used Ubuntu as a daily OS in something like 12 years so I guess I had just forgotten this
12:45:38 sean-k-mooney ya i use it daily so i swap between the two depening on what behavior i want
12:45:51 jkulik upgrade will also hold back packages needing new dependencies to be installed or other packages to be uninstalled. not only reboots. at least in debian.
12:46:07 sean-k-mooney jkulik: correctg
12:46:19 sean-k-mooney upgrade is more concervitive
12:47:05 sean-k-mooney lyarwood: how did that affect that bug
12:47:44 sean-k-mooney was brctl not upgraded?
12:49:20 sean-k-mooney lyarwood: also why are you using 16.04? aren't all stable brnaches that use that em at this point?
12:54:40 lyarwood sean-k-mooney: deploying stable/queens
12:54:58 sean-k-mooney i think queens runs fine on 18.04 as well
12:55:02 sean-k-mooney but ok
12:55:20 lyarwood sean-k-mooney: as you said in that bug it appears that something in the kernel changed during the lifecycle of that release
12:55:26 lyarwood sean-k-mooney: yeah I was just copying CI
12:55:26 sean-k-mooney i had completely forgoten about that bug report so thanks for marking it invalid
12:56:08 lyarwood np
13:01:17 artom gibi, thanks for the cleanup :)
13:02:12 artom I would have been even more agressive - like https://review.opendev.org/#/c/525335 is from 2 years ago with no response
13:02:27 artom But I won't tell you how to do your job ;)
13:03:31 openstackgerrit waleed mousa proposed openstack/os-vif master: [Follow Up] OVS DPDK port representors support https://review.opendev.org/705018
13:04:29 luyao artom: Hi
13:04:29 ygk_12345 hi all
13:04:40 ygk_12345 i have rocky setup.
13:05:10 ygk_12345 when I try to launch an instance on a specific compute node , it is throwing this error in the nova-compute logs
13:05:12 ygk_12345 Failed to retrieve resource provider tree from placement API for UUID ea3af0ff-fb69-449a-b484-5ac722010a1f
13:07:29 gibi artom: you recently asked questions on https://review.opendev.org/#/c/525335 so I allow the author to answer. :)
13:07:39 sean-k-mooney ygk_12345: does the vm launch correctly
13:08:02 ygk_12345 sean-k-mooney no . it is going into error state
13:08:12 sean-k-mooney ygk_12345: i cant recall which release we made placmenert mandatory but have you deployed the placement service
13:08:38 ygk_12345 sean-k-mooney its rocky 18.1.9 branch in openstack ansible
13:09:08 sean-k-mooney did you delete the compute node and recreate it?
13:09:42 ygk_12345 sean-k-mooney i tried upgrading the working rocky setup to stein . it failed and so rolled back to rocky now
13:09:47 ygk_12345 yes
13:10:02 ygk_12345 sean-k-mooney how to delete the compute node ?

Earlier   Later