[jira] [Commented] (AMBARI-15894) After adding support for real jdbc jar names, verify the post Ambari upgrade nothing breaks

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

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

Hadoop QA commented on AMBARI-15894:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12798787/AMBARI-15894.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/6457//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6457//console

This message is automatically generated.

> After adding support for real jdbc jar names, verify the post Ambari upgrade nothing breaks
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15894
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15894
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15894.patch
>
>
> Lets think through the upgrade scenario again:
> Prior to upgrade we know of hard-coded names and the system is in working state
> During upgrade, lets pre-populate the ambari.properties file with the old hard-coded values (think of them as the real names as thats what we know)
> If user wants to use real name, they can call ambari-server setup ...
> Net goal is to not have user do anything post Ambari upgrade.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)