remove single-nova-consoleauth configuration mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Fix Released
|
Medium
|
Unassigned | ||
OpenStack Nova Compute Charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Still trying to figure out what happened here.
Deploy failed because several hooks continued to run and the deployment timed out.
image-service-
hanode-
quantum-
cluster-
Nova-compute log is full of this:
2018-07-13 04:30:36.018 1080384 WARNING nova.conductor.api [req-943a2756-
2018-07-13 04:31:36.032 1080384 WARNING nova.conductor.api [req-943a2756-
2018-07-13 04:32:36.046 1080384 WARNING nova.conductor.api [req-943a2756-
2018-07-13 04:33:36.059 1080384 WARNING nova.conductor.api [req-943a2756-
2018-07-13 04:34:36.070 1080384 WARNING nova.conductor.api [req-943a2756-
2018-07-13 04:35:36.084 1080384 WARNING nova.conductor.api [req-943a2756-
2018-07-13 04:36:36.097 1080384 WARNING nova.conductor.api [req-943a2756-
Changed in charm-nova-cloud-controller: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 19.04 |
summary: |
- Nova Fails to come up completely. + remove single-nova-consoleauth configuration mode |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
The nova-compute messages are just due to incomplete configuration as hooks have not completed execution