Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.5.1
-
None
Description
PROBLEM:
If Custom *-site properties are added to a non-default config group in Ambari 2.5.0 or 2.5.1, these same properties will be set to "Undefined" in the default config group when a different default configuration group property for the same service is modified.
BUSINESS IMPACT:
This can result in services failing to restart for certain properties (e.g. hive.server2.thrift.bind.host)
STEPS TO REPRODUCE:
1. Install Ambari-2.5
2. Create config group for any service.
3. Add override for this new group in some custom *-site.
4. Make change in default config group for the same service.
EXPECTED RESULT:
Property overriden in step 3 will not exist in default config group
ACTUAL RESULT:
Property overriden in step 3 has value "Undefined"
Attachments
Attachments
Issue Links
- is duplicated by
-
AMBARI-24382 Ambari shouldn't deployed "Undefined" Config Values
- Resolved