[vCenter] Re-deployment has failed after deletion of controller node
Bug #1534604 reported by
Ilya Bumarskov
This bug report is a duplicate of:
Bug #1472230: Pacemaker shows healthy status for rabbitmq node meanwhile the node is actually down/split brain.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Triaged
|
High
|
Igor Gajsin | ||
Bug Description
Fuel 8.0 ISO #427
Enviroment:
Compute: QEMU + vCenter
Networking Setup: Neutron with VMware DVS (ML2 plugin)
Storage backends: default
Additional services: all by default
Nodes:
Controller
Controller
Controller
Controller
Compute + Cinder
Cinder-vmware
Compute-vmware
Steps to reproduce:
1. Delete controller node
2. Deploy changes
Observed behavior:
Deployment has failed with error:
[836] Task '{"priority"=>3000, "type"=>"puppet", "id"=>"
| Changed in fuel: | |
| importance: | Undecided → High |
| assignee: | nobody → Partner Centric Engineering (fuel-partner-engineering) |
| milestone: | none → 8.0 |
| tags: | added: area-partners vcenter |
Revision history for this message
| Ilya Bumarskov (ibumarskov) wrote | #1 |
| description: | updated |
| Changed in fuel: | |
| assignee: | Partner Centric Engineering (fuel-partner-engineering) → Igor Gajsin (igajsin) |
| status: | New → Triaged |
Revision history for this message
| Igor Gajsin (igajsin) wrote | #2 |
To post a comment you must log in.
Problem was in the core (see according bug) and it's fixed already.
At least in the Fuel #456 ISO this bug can't be reproduced.