Configuration changes must be forbidden during deployment

Bug #1531528 reported by Aleksey Kasatkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Medium
Fuel Sustaining
8.0.x
Won't Fix
Medium
Fuel Python (Deprecated)
Mitaka
Won't Fix
Medium
Fuel Python (Deprecated)
Newton
Confirmed
Medium
Fuel Sustaining

Bug Description

Version: 8.0 and earlier

User should not be allowed to change configuration during deployment (when environment is in 'deployment' status or nodes are in 'provisioning' or 'deploying' status). Such changes may lead to undesired/unexpected behaviour from user point of view. I.e. most settings will be actually applied during the next deployment of this environment/node but configuration in DB will be changed immediately. And behaviour for 'apply changes' and 'provision/deploy selected nodes' will be different. This refers to cluster, nodes, node groups, networking configuration. It is already covered for cluster and partly for networking and nodes. It is required to cover all related API.

Artem Roma (aroma-x)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Ihor Kalnytskyi (ikalnytskyi) wrote :

Why it's high prio for 8.0? I'd mark it as medium, and move to 9.0. It's about improving UX, not about fixing actual bugs.

Changed in fuel:
milestone: 8.0 → 9.0
importance: High → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.