Magnum Bay Update does not result in update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When attempting to update the node_count of an existing cluster, the cluster never enters UPDATE_IN_PROGRESS state. Examination of the magnum-conductor logs reveals the following error:
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
2016-10-24 19:17:50.717 10948 ERROR oslo_messaging.
Changed in magnum: | |
status: | New → Confirmed |
assignee: | nobody → Jaycen Grant (jaycen-v-grant) |
This is a duplicate to https:/ /bugs.launchpad .net/magnum/ +bug/1636050.
A fix has been submitted https:/ /review. openstack. org/#/c/ 390143/