Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.5.0
-
None
Description
Say property A, when set to a specific value, needs property B and C. But property B and C do not exist in the config bag. This could be due to them being optional and hence deleted or its after Ambari upgrade and the optional properties B and C are not added.
Now if stack advisor throws validation warnings that B and C must exist and have a valid values those warnings are not shown in the UI.
Fixing this behavior is also critical as we are trying not to add optional properties when Ambari is upgraded to avoid service restarts.
Attachments
Attachments
Issue Links
- links to