After cluster reboot, nova-compute stays blocked with "Services not running that should be: nova-compute"
Bug #1829003 reported by
Jason Hobbs
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Nova Compute Charm |
Triaged
|
High
|
Unassigned | ||
Bug Description
After performing a full cluster reboot of my FCB, I recovered mysql and waited a bit for things to recover.
One of my nova-compute units, nova-compute-kvm/3, stayed in blocked state because the nova-compute service wasn't running.
bundle: http://
I was able to get past this by starting the nova-compute service manually on the node.
crashdump: http://
| description: | updated |
| Changed in charm-nova-compute: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: cold-start |
To post a comment you must log in.
