[AMBARI-4921] Provisioning cluster via API is broken due to global/user_group configuration property being required

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Assignee: Siddharth Wagle Assign to me
• Reporter: John Speidel
• Created: 03/Mar/14 16:55
• Updated: 15/May/14 23:27
• Resolved: 15/May/14 23:27

Description

The configuration property "global/user_group" is now required for cluster install but not included in the stack configuration. Instead, this property is only set via the Ambari UI. Clients who currently provision clusters via the Ambari REST API are now broken due to the addition of this property. This includes OpenStack Savanna and Ambari Blueprints.

There are 2 issues here.

• A new required configuration was added. Existing users of the API will not know to provide this configuration property and will therefore be broken. This property shouldn't be required and should have a default if not specified.
• This property should be included in all of the stack definitions that require it. The work being done in Ambari Blueprints uses the stack configurations as defaults and since this property is not included in the stack definition, it is not being set which causes an install failure.