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

Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2016/07/05 16:43:11 UTC

[jira] [Reopened] (AMBARI-17564) Identify config changes added to Ambari-2.4.0 and mark them to not get added during Ambari upgrade

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

Dmitry Lysnichenko reopened AMBARI-17564:
-----------------------------------------

We decided to revert it for now.

> Identify config changes added to Ambari-2.4.0 and mark them to not get added during Ambari upgrade
> --------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17564
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17564
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17564.patch
>
>
> Now that we have the mechanism to prevent configs from getting added as part of Ambari upgrade, lets identify the configs that got added in 2.4.0 and mark them as not to be added during Ambari upgrade.



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