[jira] [Commented] (AMBARI-20365) Display Ranger DB backup instruction in sections on the manual step during RU

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-20365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902406#comment-15902406 ] 

Hadoop QA commented on AMBARI-20365:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12856869/AMBARI-20365.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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/10932//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10932//console

This message is automatically generated.

> Display Ranger DB backup instruction in sections on the manual step during RU
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-20365
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20365
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: AMBARI-20365.patch
>
>
> current approach is to use multiple <message> sections. Alejandro also suggested an alternative where a single <message> section can accept HTML markup for greater flexibility.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)