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

Hadoop QA commented on AMBARI-8532:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12684940/AMBARI-8532.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 patch failed these unit tests in 
ambari-admin ambari-server:

                  
org.apache.ambari.server.controller.AmbariManagementControllerTest

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

This message is automatically generated.

> Rolling Upgrade Bootstrap - Populate repo_version table during cluster 
> creation
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-8532
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8532
>             Project: Ambari
>          Issue Type: Technical task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8532.patch
>
>
> Creating a cluster needs to populate the repo_version table with the same 
> stack name and stack version that is used in the cluster_version table.



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

Reply via email to