Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 12 Sep 2016 09:46:20 +0000 (UTC)
From: "Gonzalo Herreros (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13004267.1473673542000.546200.1473673580615@Atlassian.JIRA>
In-Reply-To: <JIRA.13004267.1473673542000@Atlassian.JIRA>
References: <JIRA.13004267.1473673542000@Atlassian.JIRA> <JIRA.13004267.1473673542579@arcas>
Subject: [jira] [Updated] (AMBARI-18358) Deleting a service with node
 specific configuration makes Ambari unstable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 12 Sep 2016 09:46:22 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-18358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gonzalo Herreros updated AMBARI-18358:
--------------------------------------
    Description: 
Always reproduced.

On any service, change some setting to be node specific (instead of global to the cluster). 
To do so create a config group, switch to it and change some setting to be specific for that group.

Now, stop and delete the service. The configuration is deleted but the group configuration is left behind.

From this moment the log will be full of " Config inconsistency exists: unknown configType=dbks-site" (in my case the service I reproduced it was Ranger KMS).
Any attempt to add a service will get a 500.

The only workaround is going to the DB and manually delete the group configuration.

  was:
Always reproduced.

On any service change some setting to be node specific (instead of global to the cluster). To do so create a config group, switch to it and change some setting to be specific for that group.

Now, stop and delete the service. The configuration is deleted but the group configuration is left behind.

From this moment the log will be full of " Config inconsistency exists: unknown configType=dbks-site" (in my case the service I reproduced it was Ranger KMS).
Any attempt to add a service will get a 500.

The only workaround is going to the DB and manually delete the group configuration.


> Deleting a service with node specific configuration makes Ambari unstable
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-18358
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18358
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: 2.4.0
>            Reporter: Gonzalo Herreros
>
> Always reproduced.
> On any service, change some setting to be node specific (instead of global to the cluster). 
> To do so create a config group, switch to it and change some setting to be specific for that group.
> Now, stop and delete the service. The configuration is deleted but the group configuration is left behind.
> From this moment the log will be full of " Config inconsistency exists: unknown configType=dbks-site" (in my case the service I reproduced it was Ranger KMS).
> Any attempt to add a service will get a 500.
> The only workaround is going to the DB and manually delete the group configuration.


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