Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 19 Jul 2016 13:42:20 +0000 (UTC)
From: "Robert Levas (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12990765.1468935726000.72032.1468935740614@Atlassian.JIRA>
In-Reply-To: <JIRA.12990765.1468935726000@Atlassian.JIRA>
References: <JIRA.12990765.1468935726000@Atlassian.JIRA> <JIRA.12990765.1468935726181@arcas>
Subject: [jira] [Created] (AMBARI-17790) Adding new components for existing
 services should process Kerberos-related configuration changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 19 Jul 2016 13:42:22 -0000

Robert Levas created AMBARI-17790:
-------------------------------------

             Summary: Adding new components for existing services should process Kerberos-related configuration changes
                 Key: AMBARI-17790
                 URL: https://issues.apache.org/jira/browse/AMBARI-17790
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.1
            Reporter: Robert Levas
            Assignee: Robert Levas
             Fix For: 2.5.0


When adding new components for existing services, Kerberos-related configuration changes should be processed.  This should happen when an new component, not a new instance of an existing component is installed. 

Care must be taken to not reintroduce the issue described in AMBARI-14506 or if unavoidable, proper documentation should be added 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)