Improper behavior for reset environment
Bug #1286024 reported by
Nastya Urlapova
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Nikolay Markov |
Bug Description
iso #225
Deploy simple cluster:
1xController
1xCompute
After successful deploy push "Reset environment".
Add some new option for cluster and add one compute node for example.
Old stuff have discovered status and possible to deploy changes.
Changed in fuel: | |
importance: | Critical → High |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Nikolay Markov (nmarkov) |
status: | Triaged → In Progress |
tags: | added: in progress |
Changed in fuel: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
We have here several problems
1. dissipated node, somehow this node was assigned to another cluster (see nailgun/api.log)
2. deployment wasn't started on nodes which were reseted, it looks like deploy button was pressed before nodes was moved to discovery state