3 reset_environment tasks in cluster after it has been reset
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Anastasia Balobashina | ||
Mitaka |
Fix Released
|
High
|
Anastasia Balobashina | ||
Newton |
Fix Released
|
High
|
Anastasia Balobashina | ||
Ocata |
Fix Committed
|
High
|
Anastasia Balobashina |
Bug Description
Reproduced on fake ui:
1) Deploy default environment with 1 controller
2) Reset deployment
Expected result: there is one 'reset_deployment' task in GET /api/tasks?
Actual result: there is 3 'reset_deployment' tasks in GET /api/tasks?
[{"status": "ready", "name": "reset_
And one of the has double message: "Environment '1' was successfully reset\nEnvironment '1' was successfully reset"
Please consider also an attached screenshot of Fuel UI.
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: team-bugfixx |
tags: |
added: team-bugfix removed: team-bugfixx |
tags: | added: feature-reset-env |
Changed in fuel: | |
assignee: | Fuel Python (Deprecated) (fuel-python) → Fuel Sustaining (fuel-sustaining-team) |
Changed in fuel: | |
importance: | Medium → High |
tags: | added: on-verification |
We have a strong rule not to backport Medium priority bugs.