nova-compute charm workload status should block on inclusion in hypervisor list
Bug #1775690 reported by
Ryan Beisner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
When the nova-compute charm is deployed, it is possible for the charm to represent a READY/OK workload state when in fact the compute hypervisor is not registered with nova successfully.
We should change that. The charm application and unit workload states should block until we confirm that the compute node is successfully registered with nova as a hypervisor.
Changed in charm-nova-compute: | |
milestone: | 18.08 → 18.11 |
Changed in charm-nova-compute: | |
milestone: | 18.11 → 19.04 |
Changed in charm-nova-compute: | |
milestone: | 19.04 → 19.07 |
Changed in charm-nova-compute: | |
milestone: | 19.07 → 19.10 |
Changed in charm-nova-compute: | |
milestone: | 19.10 → 20.01 |
Changed in charm-nova-compute: | |
milestone: | 20.01 → 20.05 |
Changed in charm-nova-compute: | |
milestone: | 20.05 → 20.08 |
Changed in charm-nova-compute: | |
milestone: | 20.08 → none |
To post a comment you must log in.
Reference, where a compute node fails to register as a hypervisor, yet the Juju status is green: /bugs.launchpad .net/charm- nova-compute/ +bug/1771662
https:/
The rest of that bug is unrelated, but it is a good example for this bug.