Environment settings unexpectedly locked because of restriction
Bug #1527252 reported by
Julia Aranovich
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Low
|
Fuel UI Team | ||
| Mitaka |
Won't Fix
|
Low
|
Fuel UI Team | ||
| Newton |
Confirmed
|
Low
|
Fuel UI Team | ||
Bug Description
When some environment setting has 'cluster:is_locked' restriction then the setting becomes locked in a new not deployed environment.
Using the restriction to 'cluster:is_locked == true' works correctly, settings won't be locked in a new environment.
Because of this restriction is barely used in UI, the ticket has 'Low' priority.
| Changed in fuel: | |
| status: | Confirmed → Won't Fix |
Revision history for this message
| Kate Pimenova (kpimenova) wrote | #1 |
| Changed in fuel: | |
| milestone: | 10.0 → 11.0 |
| status: | Won't Fix → Confirmed |
To post a comment you must log in.
The reason of this issue is:
Restriction with structure like 'cluster:is_locked' after expression parser - becomes Modelpath instead of Subexpression,
so satisfiedRestri