Invalid settings after Load Defaults

[Julia Aranovich]

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.

[Julia Aranovich (jkirnosova)]

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.

[Julia Aranovich (jkirnosova)]

An issues from the previous comment are fixed in 5.1.

[Alexandra Morozova (astepanchuk)]

What shall be the workaround here? Isn't this ticket a part of Invalid tabs concept?

[Julia Aranovich (jkirnosova)]

No workaround.

This can be considered as a part of Invalid Tabs functionality. But until it will be designed and implemented I suggest to load setting defaul values once the tab opened and check environment role limits on these default values. And make a decision about Load Defaults button disabled state.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/207442

[OpenStack Infra (hudson-openstack)]

Change abandoned by Alexandra Morozova (<email address hidden>) on branch: master
Review: https://review.openstack.org/207442
Reason: this change requires lots of refactoring to be implemented correctly I suggest moving to the next release