Deployment failure on one node leads to erasing of all nodes of the environment
Bug #1597130 reported by
Eugene Nikanorov
This bug report is a duplicate of:
Bug #1529691: Stop deployment while adding compute node to existing cluster leads to the destruction of the cluster.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Incomplete
|
High
|
Maksim Malchuk | ||
| 7.0.x |
Incomplete
|
High
|
Maksim Malchuk | ||
Bug Description
Per astute log, some deployment action has stuck on one node out of many and was forcefully stopped, by killing corresponding fuel task;
that has triggered erasing of all nodes and basically caused the loss of whole cloud.
I'm attaching the astute.log where around 2016-06-28T00:17:11 these events can be observed.
Revision history for this message
| Eugene Nikanorov (enikanorov) wrote | #1 |
| tags: | added: customer-found |
Revision history for this message
| Eugene Nikanorov (enikanorov) wrote | #3 |
| summary: |
- Deployment failure on one node leads to erasing of all nodes + Deployment failure on one node leads to erasing of all nodes of the + environment |
| description: | updated |
Revision history for this message
| Dmitry Klenov (dklenov) wrote | #4 |
Revision history for this message
| Eugene Nikanorov (enikanorov) wrote | #5 |
| no longer affects: | fuel/newton |
| tags: | added: area-library |
| Changed in fuel: | |
| assignee: | Fuel Sustaining (fuel-sustaining-team) → Maksim Malchuk (mmalchuk) |
To post a comment you must log in.
Found with Fuel 7.0