[
https://issues.apache.org/jira/browse/AMBARI-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470628#comment-15470628
]
Hudson commented on AMBARI-18278:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5629 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5629/])
AMBARI-18278. Provide Notes On Service Config Changes During Ambari
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8755bf91e2a728132262669b50713388cf08b8db])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> Provide Notes On Service Config Changes During Ambari Upgrade
> -------------------------------------------------------------
>
> Key: AMBARI-18278
> URL: https://issues.apache.org/jira/browse/AMBARI-18278
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18278.2.patch, AMBARI-18278.patch
>
>
> For every configuration change made, a meaningful note should be included so
> that administrators understand why so many versions are being created. Any of
> the following would be fine:
> - Ambari Upgrade updated storm-site
> - Ambari Upgrade from 2.2.0 to 2.4.0 changed storm-site
> - The following configurations were changed as part of the Ambar Server
> Upgrade: storm-site
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
