You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Gonzalo Herreros (JIRA)" <ji...@apache.org> on 2016/09/12 09:46:20 UTC

[jira] [Created] (AMBARI-18358) Deleting a service with node specific configuration makes Ambari unstable

Gonzalo Herreros created AMBARI-18358:
-----------------------------------------

             Summary: 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)