[nodegroups] Slaves behavior is unpredictable after environment removal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Newton |
Confirmed
|
Medium
|
Fuel Sustaining |
Bug Description
Fuel version (8.0 build #231): http://
There are 3 possible states if slave nodes from non-default nodegroup after environment is removed:
1) nodes are erased, bootstrapped and marked as 'error' (because there is no nodegroup for them)
2) nodes are erased and bootstrapped, but not discovered, because during bootstrap they failed to get IP address via DHCP
3) nodes are erased, but not bootstrapped - PXE boot failed
Nodes get states #2 or #3 when nodegroup is removed before they are bootstrapped/
In my opinion Fuel should either always put such nodes to state #3 (remove nodegroup before slaves restart) or don't remove nodegroup at all (detach it from environments).
tags: | added: area-python |
Changed in fuel: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: swarm-blocker |
tags: | removed: swarm-blocker |
tags: | added: team-network |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: keep-in-9.0 |
Changed in fuel: | |
milestone: | 10.0 → 11.0 |
assignee: | Registry Administrators (registry) → Fuel Sustaining (fuel-sustaining-team) |
Related fix proposed to branch: master /review. openstack. org/251968
Review: https:/