ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17564) Identify config changes added to Ambari-2.4.0 and mark them to not get added during Ambari upgrade
Date Tue, 12 Jul 2016 16:20:20 GMT

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

Dmitry Lysnichenko updated AMBARI-17564:
----------------------------------------
    Fix Version/s:     (was: 2.5.0)
                   2.4.0

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

Mime
View raw message