ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Toader (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15200) Unusable configs after creating override
Date Fri, 26 Feb 2016 12:31:18 GMT

     [ 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)

Mime
View raw message