[
https://issues.apache.org/jira/browse/AMBARI-20871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987170#comment-15987170
]
Hadoop QA commented on AMBARI-20871:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12865387/AMBARI-20871.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11515//console
This message is automatically generated.
> Unify repository file creation
> ------------------------------
>
> Key: AMBARI-20871
> URL: https://issues.apache.org/jira/browse/AMBARI-20871
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Nate Cole
> Assignee: Nate Cole
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20871.patch
>
>
> Repo files are written two different ways in Ambari. The first way makes
> each repository its own file:
> {noformat}
> # cat /etc/yum.repos.d/HDP.repo
> [HDP-2.5]
> name=...
> baseurl=...
> path=/
> enabled=1
> # cat /etc/yum.repos.d/HDP-UTILS.repo
> [HDP-UTILS-1.1.0.21]
> name=...
> baseurl=...
> path=/
> enabled=1
> {noformat}
> With installing packages for upgrade purposes, only ONE file is created:
> {noformat}
> # cat /etc/yum.repos.d/HDP-2.5.3.0-38.repo
> [HDP-2.5.3.0-38]
> ...
> [HDP-UTILS-2.5.3.0-38]
> ...
> {noformat}
> This behavior should be unified as in the 2nd behavior. This is going to be
> important to be able to support multiple deployed versions, per host, as is
> required for PU/CU.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
