Invalid settings after Load Defaults
Bug #1342684 reported by
Julia Aranovich
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel UI Team | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel UI Team | ||
Newton |
Confirmed
|
Medium
|
Fuel UI Team |
Bug Description
1. Create new env
2. Enable Ceilometer on Settings tab
3. Add Mongo nodes to the env.
4. Go to Settings tab. Ceilometer checkbox is locked
5. Click Load Defaults button
Actual result: Ceilometer has default False value, but Mongo nodes presented in the env. So, we get invalid env configuration.
Changed in fuel: | |
assignee: | Fuel UI Team (fuel-ui) → Julia Aranovich (jkirnosova) |
summary: |
- Invalid settings after Load Defaults + [ui] Invalid settings after Load Defaults |
Changed in fuel: | |
assignee: | Julia Aranovich (jkirnosova) → Fuel UI Team (fuel-ui) |
summary: |
- [ui] Invalid settings after Load Defaults + [ui] [settings] Invalid settings after Load Defaults |
Changed in fuel: | |
milestone: | 6.0 → 6.1 |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
tags: | added: qa-agree-7.0 |
Changed in fuel: | |
assignee: | Fuel UI Team (fuel-ui) → Alexandra Morozova (astepanchuk) |
Changed in fuel: | |
assignee: | Alexandra Morozova (astepanchuk) → Fuel UI Team (fuel-ui) |
status: | In Progress → Confirmed |
tags: | added: tricky |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
tags: | added: area-ui |
summary: |
- [ui] [settings] Invalid settings after Load Defaults + Invalid settings after Load Defaults |
Changed in fuel: | |
status: | Confirmed → Won't Fix |
Changed in fuel: | |
milestone: | 10.0 → 11.0 |
status: | Won't Fix → Confirmed |
To post a comment you must log in.
The following case has the same essence:
a setting has several values which dont' contradict restrictions of some dependent setting. If this dependent setting is active, the initial setting should not be locked. But in this case user can set a value of initialSetting that contradicts dependent setting restrictions. We got invalid settings structure.
This case can be supported for radio groups but not for text settinngs.