[
https://issues.apache.org/jira/browse/AMBARI-15916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247620#comment-15247620
]
Hadoop QA commented on AMBARI-15916:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12799450/AMBARI-15916.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6530//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6530//console
This message is automatically generated.
> 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)
