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

Hadoop QA commented on AMBARI-10945:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12730661/AMBARI-10945.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {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/2632//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2632//console

This message is automatically generated.

> Create a mainrepoid field in repoinfo.xml to indicate which repo base url 
> will be updated
> -----------------------------------------------------------------------------------------
>
>                 Key: AMBARI-10945
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10945
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Bryan Cutler
>            Assignee: Bryan Cutler
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-10945.patch
>
>
> During the Ambari upgrade process, StackUpgradeUtil.updateLocalRepo() 
> attempts to update the base URL of a repository with the assumption that the 
> repoid will be in the form "stackName-stackVersion."  If the repoid does not 
> follow this, there is an error and the upgrade process can not continue.
> I propose that we add an optional field in repoinfo.xml that can define a 
> "main" repository to be updated so that there is no assumption of the repoid. 
>  If this field is not provided, then it will fall back to updating a repoid 
> with "stackName-stackVersion."



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

Reply via email to