TypeError in _get_inventory_and_update_provider_generation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Matt Riedemann | ||
Pike |
Fix Committed
|
Medium
|
Oliver Walsh | ||
Queens |
Fix Committed
|
Medium
|
Oliver Walsh |
Bug Description
Description
===========
Bringing up a new cluster as part of our CI after switch from 16.1.0 to 16.1.1 on Centos, I'm seeing this error on some computes:
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
2018-04-26 13:36:26.580 14536 ERROR nova.compute.
The error seems persistent for a single run of nova-compute.
Steps to reproduce
==================
Nodes were started by our CI infrastructure. We start 3 computes and a single control node. In 50% of cases, one of the computes comes up in this bad state.
Expected result
===============
Working cluster.
Actual result
=============
At least one of 3 nodes fails to join the cluster, it's not picked up by discover_hosts and I see the above stack trace repeated in the nova-compute logs.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
$ rpm -qa | grep nova
python-
openstack-
python2-
openstack-
openstack-
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
$ rpm -qa | grep kvm
libvirt-
qemu-kvm-
qemu-kvm-
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
Not sure
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
Neutron with Calico (I work on Calico, this is our CI system)
tags: | added: placement |
This problem, I also encountered.