Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CF72E186A3 for ; Wed, 28 Oct 2015 19:26:49 +0000 (UTC) Received: (qmail 81233 invoked by uid 500); 28 Oct 2015 19:26:28 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 81210 invoked by uid 500); 28 Oct 2015 19:26:28 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 81182 invoked by uid 99); 28 Oct 2015 19:26:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2015 19:26:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BD13B2C1F57 for ; Wed, 28 Oct 2015 19:26:27 +0000 (UTC) Date: Wed, 28 Oct 2015 19:26:27 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-13551) When adding components to a Kerberized cluster, the set of hosts to create principals for should be limited to only the relevant set MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-13551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979076#comment-14979076 ] Hudson commented on AMBARI-13551: --------------------------------- FAILURE: Integrated in Ambari-branch-2.1 #760 (See [https://builds.apache.org/job/Ambari-branch-2.1/760/]) AMBARI-13551. When adding components to a Kerberized cluster, the set of (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ef387bf8cb8abad87eab22da61c57e90b2ebb411]) * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareDisableKerberosServerAction.java * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java * ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/PrepareKerberosIdentitiesServerAction.java * ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java * ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java > When adding components to a Kerberized cluster, the set of hosts to create principals for should be limited to only the relevant set > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: AMBARI-13551 > URL: https://issues.apache.org/jira/browse/AMBARI-13551 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.1.3 > Reporter: Robert Levas > Assignee: Robert Levas > Priority: Critical > Labels: kerberos > Fix For: 2.1.3 > > Attachments: AMBARI-13551_branch-2.1_01.patch, AMBARI-13551_trunk_01.patch > > > When adding components to a Kerberized cluster, the set of hosts to create principals for should be limited to only the relevant set. This is because if a component for an existing service is added to an existing host, principals and keytab files for the existing components will get unnecessarily updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)