Role and Name of the node is not discarded after deleting environment if node was in discarded state
Bug #1277081 reported by
Andrey Sledzinskiy
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Evgeniy L |
Bug Description
Bug is reproduced on fuel-4.
Steps:
1. Create new environment with all default values
2. Open Nodes tab
3. Click Add nodes
4. Assign Compute role to any Node and change Node name to 'Test compute node'
5. Click Apply Changes – changes are saved and page with added nodes is present
6. Click 'discard addition' for added Node
7. Delete Environment
8. Wait until all nodes are discovered again
9. Create new environment
10. Open nodes tab and click Add nodes
Expected – all nodes are with 'untitled' name and 'unallocated' role
Actual – discarded node is with Compute role and 'Test compute node' name (see attach DiscardedNodeRe
Changed in fuel: | |
status: | New → Confirmed |
assignee: | nobody → Fuel Python Team (fuel-python) |
Changed in fuel: | |
importance: | Medium → High |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Evgeniy L (rustyrobot) |
status: | Confirmed → In Progress |
tags: | added: in progress |
tags: | removed: in progress |
To post a comment you must log in.
I think we should change unassignment logic, as I know Alexander is working on this task https:/ /bugs.launchpad .net/fuel/ +bug/1265036 and maybe it can be solved as part of his task.
But REST api will be changed, for assignment and assignment will be implemented separate handlers. /bugs.launchpad .net/fuel/ +bug/1265036/ comments/ 2
https:/