Cluster is not locked during running separated provisioning or deployment task
Bug #1587792 reported by
Julia Aranovich
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Bulat Gaifullin | ||
Mitaka |
Fix Released
|
High
|
Bulat Gaifullin |
Bug Description
Steps to reproduce in Fuel UI:
1) create an environment, add a node
2) go to Dashboard and start provisioning of the node (Provisioning Only mode)
3) go to Networks/Settings tabs
Expected result: all inputs are locked on the tabs.
Actual result: no inputs locked, cluster's is_locked attribute comes as False from Nailgun.
Changed in fuel: | |
assignee: | nobody → Fuel Toolbox (fuel-toolbox) |
Changed in fuel: | |
assignee: | Fuel Toolbox (fuel-toolbox) → Bulat Gaifullin (bgaifullin) |
To post a comment you must log in.
We don't have "provisioning" cluster state and as the result there is no lock on it.
It is possible to detect nodes in provisioning state and make decision on UI side or make according cluster flag like "is_provisioning" on server side. Obvious variant of making cluster "provisioning" state looks very invasive and all business logic now relying on fact that provisioning of new node not blocking any other operations on cluster.