[
https://issues.apache.org/jira/browse/AMBARI-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250687#comment-15250687
]
Hudson commented on AMBARI-15916:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4696 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4696/])
AMBARI-15916. Handle upgrade scenarios when db audit option is removed (gautam:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ee95300414803f77e875a3272e6d2d0ecf24f16b])
*
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py
*
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
> Handle upgrade scenarios when db audit option is removed for Ranger
> -------------------------------------------------------------------
>
> Key: AMBARI-15916
> URL: https://issues.apache.org/jira/browse/AMBARI-15916
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Gautam Borad
> Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-15916.patch
>
>
> As part of AMBARI-15914, stack changes are done in order to remove configs
> for Audit to DB in Ranger.
> This BUG needs to cover the dev and test work to handle upgrade scenarios
> when user upgrades from Audit to DB enabled Ranger setup to latest version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
