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

["Dmitry Lysnichenko (JIRA)" <ji...@apache.org>]

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

Dmitry Lysnichenko resolved AMBARI-17564.
-----------------------------------------
    Resolution: Fixed

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   e85fc59..b7dfe39  branch-2.4 -> branch-2.4
   3c4595e..0c1830c  trunk -> trunk


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