Cluster has 'new' status after deployment
Bug #1542201 reported by
Julia Aranovich
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Bulat Gaifullin |
Bug Description
STR:
1) create default environment and add some nodes
2) start 'provisioning' task for the environment (UI sends PUT /api/clusters/
3) start 'deployment' task for the environment (UI sends PUT /api/clusters/
4) check the environment status
Expected result: the environment status should be 'operational', as well as all nodes are deployed
Actual result: the environment status is 'new'. At the same time the environment has is_locked == true attribute.
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Bulat Gaifullin (bgaifullin) |
Changed in fuel: | |
assignee: | Bulat Gaifullin (bgaifullin) → Alexey Shtokolov (ashtokolov) |
Changed in fuel: | |
assignee: | Alexey Shtokolov (ashtokolov) → Bulat Gaifullin (bgaifullin) |
tags: | added: on-verification |
tags: | added: release-notes |
tags: |
added: release-notes-done removed: release-notes |
To post a comment you must log in.
Hm.. I think it wasn't a bug. You see, by design we do not operate with cluster statuses on such low-level API calls like provision or deploy of selected nodes, and you use precisely them.
I think it should be discussed, because otherwise some use-cases may be broken.