[AMBARI-17629] AUTH_TO_LOCAL rules are not updated when adding services to a Blueprint-installed cluster

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Labels: auth_to_local kerberos
• Assignee: Robert Levas
• Reporter: Robert Levas
• Created: 08/Jul/16 18:48
• Updated: 15/Jul/16 03:24
• Resolved: 15/Jul/16 03:24

Description

When adding new services and components to a cluster that was initially created via Blueprints (rather than via the Ambari UI), auth-to-local rules that are expected to be created as indicated by the Kerberos descriptor are not.

It occurs because the components being installed are in the INIT state where the logic to determine whether to include the new auth-to-local rules or not expects the components to be in either the INSTALLED or STARTED states. This is due to logic added when resolving AMBARI-14232.

Solution:
Allow for auth-to-local rules for new services and components to be added when the state of the components are INIT as well as INSTALLED and STARTED, when the cluster was installed via Blueprints.

Issue Links

• links to: ReviewBoard