Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 25 Jul 2016 08:00:34 +0000 (UTC)
From: "Andrii Babiichuk (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12992179.1469433628000.121001.1469433634424@Atlassian.JIRA>
In-Reply-To: <JIRA.12992179.1469433628000@Atlassian.JIRA>
References: <JIRA.12992179.1469433628000@Atlassian.JIRA> <JIRA.12992179.1469433628425@arcas>
Subject: [jira] [Created] (AMBARI-17876) Delete Ranger KMS service does not
 give recommendations on dependent service config updates (FE)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 25 Jul 2016 08:00:36 -0000

Andrii Babiichuk created AMBARI-17876:
-----------------------------------------

             Summary: Delete Ranger KMS service does not give recommendations on dependent service config updates (FE)
                 Key: AMBARI-17876
                 URL: https://issues.apache.org/jira/browse/AMBARI-17876
             Project: Ambari
          Issue Type: Bug
    Affects Versions: 2.4.0
            Reporter: Andrii Babiichuk
            Assignee: Andrii Babiichuk
            Priority: Critical
             Fix For: 2.4.0


Test steps:
Install cluster with services HDFS, Yarn, MR, Hive, HBase, Ranger, Ranger KMS
Delete KMS service using Ambari UI option on Ranger KMS Summary page
Observation:
Delete is successful and KMS service gets completely removed, but the associated configs on other services are not updated, recommendations also not provided when delete triggered.
After KMS removal, HDFS, Hive, HBase side operations fail as previously few of the dirs/paths were encrypted zones and now those configs dont hold good.

Add UI Warning when removing RANGER_KMS


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