Upgrade from bionic-rocky to bionic-stein fails - no available hosts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Fix Released
|
Critical
|
Frode Nordahl | ||
OpenStack Nova Cloud Controller Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Nova Compute Charm |
Fix Released
|
Critical
|
Frode Nordahl |
Bug Description
After the upgrade from bionic-rocky to bionic-stein, you cannot launch a new instance. This is due to the listed hypervisors. Deleting the 'old' aka 'down' hypervisors allows the new ones to be registered with the placement api and instances can be launched
| ID | Hypervisor Hostname | Hypervisor Type | Host IP | State |
| 1 | juju-284597-
| 2 | juju-284597-
| 3 | juju-284597-
| 4 | juju-284597-
| 5 | juju-284597-
| 6 | juju-284597-
| ID | Hypervisor hostname | State | Status |
| 75481283-
| 5d09e737-
| 3dbaf0d0-
| 692318fc-
| 66c8dfd5-
| 506b8ae3-
$ openstack compute service list
| ID | Binary | Host | Zone | Status | State | Updated At |
| 1 | nova-scheduler | juju-284597-
| 2 | nova-conductor | juju-284597-
| 4 | nova-compute | juju-284597-
| 5 | nova-compute | juju-284597-
| 6 | nova-compute | juju-284597-
| 9 | nova-compute | juju-284597-
| 10 | nova-compute | juju-284597-
| 11 | nova-compute | juju-284597-
Changed in charm-nova-compute: | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-neutron-openvswitch: | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Frode Nordahl (fnordahl) |
milestone: | none → 19.10 |
Changed in charm-nova-compute: | |
milestone: | none → 19.10 |
Changed in charm-nova-cloud-controller: | |
status: | New → Invalid |
Changed in charm-nova-compute: | |
status: | Fix Committed → Fix Released |
Changed in charm-neutron-openvswitch: | |
status: | Fix Committed → Fix Released |
This was most likely introduced by /review. opendev. org/#/q/ topic:bug/ 1839300+ (status: open+OR+ status: merged)
https:/
The assumption made there was that if you would upgrade, you would also
come from a previous charm version.
I guess that is an incorrect assumption.
We could fix it by setting the initial kv key based on both openstack and
charm version, not just charm version.