Robert Levas created AMBARI-17629:
-------------------------------------
Summary: AUTH_TO_LOCAL rules are not updated when adding services
to a Blueprint-installed cluster
Key: AMBARI-17629
URL: https://issues.apache.org/jira/browse/AMBARI-17629
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
Fix For: 2.4.0
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
