You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2015/09/26 00:48:04 UTC

[jira] [Updated] (AMBARI-10945) Create a mainrepoid field in repoinfo.xml to indicate which repo base url will be updated

     [ https://issues.apache.org/jira/browse/AMBARI-10945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yusaku Sako updated AMBARI-10945:
---------------------------------
    Fix Version/s:     (was: 2.1.2)

> 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
>         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)