You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2016/02/26 13:31:18 UTC
[jira] [Updated] (AMBARI-15200) Unusable configs after creating
override
[ https://issues.apache.org/jira/browse/AMBARI-15200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Toader updated AMBARI-15200:
--------------------------------------
Attachment: AMBARI-15200.trunk.v1.patch
AMBARI-15200.branch-2.2.v1.patch
AMBARI-15200.2.2.1-maint.v1.patch
> Unusable configs after creating override
> ----------------------------------------
>
> Key: AMBARI-15200
> URL: https://issues.apache.org/jira/browse/AMBARI-15200
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Critical
> Fix For: 2.2.1
>
> Attachments: AMBARI-15200.2.2.1-maint.v1.patch, AMBARI-15200.branch-2.2.v1.patch, AMBARI-15200.trunk.v1.patch
>
>
> After creating override for any service (ZooKeeper for example) configs page for this service becomes unusable: not all configs are loaded and button with empty label is shown.
> The root cause of this issue is that the server API returns wrong is_current flag for default config group after creating an override.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)