when octane upgrade-node fail with compute node, it leave node in error status
Bug #1506405 reported by
Maksim Malchuk
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Won't Fix
|
Wishlist
|
Unassigned | ||
| 7.0.x |
Won't Fix
|
Low
|
Oleg S. Gelbukh | ||
| Mitaka |
Won't Fix
|
Medium
|
Oleg S. Gelbukh | ||
| Newton |
Won't Fix
|
Wishlist
|
Registry Administrators | ||
Bug Description
Irrevocable errors in upgrade of compute node: need to add idempotent reinstallation of node that was already moved to new cluster or instructions for recovery; need to handle error status on compute after upgrade, for example, delete from environment and move to discover state.
| Changed in fuel: | |
| milestone: | none → 8.0 |
| no longer affects: | fuel/8.0.x |
| tags: | added: module-octane |
| Changed in fuel: | |
| status: | New → Confirmed |
Revision history for this message
| Oleg S. Gelbukh (gelbuhos) wrote | #1 |
| tags: | added: area-octane |
| tags: |
added: area-python removed: area-octane |
| Changed in fuel: | |
| importance: | Critical → High |
Revision history for this message
| Oleg S. Gelbukh (gelbuhos) wrote | #2 |
| Changed in fuel: | |
| importance: | High → Medium |
| tags: | added: feature |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-octane (master) | #3 |
| Changed in fuel: | |
| assignee: | Fuel Octane Dev Team (fuel-octane) → Oleg S. Gelbukh (gelbuhos) |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on fuel-octane (stable/7.0) | #4 |
| Changed in fuel: | |
| milestone: | 8.0 → 9.0 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on fuel-octane (master) | #5 |
| Changed in fuel: | |
| assignee: | Oleg S. Gelbukh (gelbuhos) → Fuel Octane (fuel-octane-team) |
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
| Changed in fuel: | |
| assignee: | Registry Administrators (registry) → nobody |
To post a comment you must log in.
Currently we can't delete a node from environment without erasing data on it. Partition preservation feature doesn't cover the delete of a node. Thus, we should not delete a node from environment even if it ended up in 'error' status. The exact recovery path depends on the nature of failure.