Changing of cluster status is hardcoded in deploy task
Bug #1551271 reported by
Julia Aranovich
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
High
|
Fuel Sustaining | ||
Bug Description
There is inconsistency in changing a cluster status logic:
1) when user starts a common 'deploy' task for a cluster, then the cluster gets 'deployment' status while the task is running
2) at the same time separate 'provision' and 'deployment' task do not change a cluster status (it is 'new' for a provisioning cluster and 'partially_
I think this logic of changing of a cluster status should be revised and unified.
| Changed in fuel: | |
| status: | New → Confirmed |
| Changed in fuel: | |
| importance: | Undecided → High |
| tags: | added: tech-debt |
Revision history for this message
| Dmitry Pyzhov (dpyzhov) wrote | #1 |
| Changed in fuel: | |
| milestone: | 9.0 → 10.0 |
| Changed in fuel: | |
| assignee: | Fuel Python (Deprecated) (fuel-python) → Fuel Sustaining (fuel-sustaining-team) |
To post a comment you must log in.
Should we get rid of cluster status completely?