[nailgun] nodes don't return to discovered state
Bug #1273006 reported by
Andrew Woodward
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Sustaining | ||
Newton |
Triaged
|
Medium
|
Fuel Sustaining |
Bug Description
case: if a node was previously in an error or deployed state, and for whichever reason the administrator want's to reset it. they should be able to force the node to load the discovery image and the node should switch status back to the discovered state.
If you force the node back into the discovered image it doesn't return to the discovered state, it just sits at its old state even though it should transition back to discovered so that tools can perform the necessary steps to re-provision/deploy
Changed in fuel: | |
status: | New → Triaged |
Changed in fuel: | |
milestone: | none → 4.1 |
Changed in fuel: | |
milestone: | 4.1 → 5.0 |
Changed in fuel: | |
milestone: | 5.0 → 5.1 |
tags: | removed: multi-l3 |
summary: |
- nodes don't return to discovered state + [nailgun] nodes don't return to discovered state |
Changed in fuel: | |
milestone: | 5.1 → 6.0 |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
Changed in fuel: | |
status: | Triaged → Confirmed |
tags: | added: feature |
Changed in fuel: | |
milestone: | 6.1 → next |
tags: | removed: nailgun |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Maciej Kwiek (maciej-iai) |
Changed in fuel: | |
assignee: | Maciej Kwiek (maciej-iai) → Fuel Python Team (fuel-python) |
Changed in fuel: | |
milestone: | next → 7.0 |
tags: | removed: feature |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
Changed in fuel: | |
status: | Confirmed → Triaged |
tags: | added: area-python |
To post a comment you must log in.
Hi Andrew,
It looks like reset environment feature https:/ /blueprints. launchpad. net/fuel/ +spec/nailgun- reset-env , doesn't it?