[
https://issues.apache.org/jira/browse/AMBARI-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211605#comment-14211605
]
Hadoop QA commented on AMBARI-8319:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12681415/AMBARI-8319_branch-1.7.0.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/639//console
This message is automatically generated.
> HDP-UTILS repo URL reverts to default on ambari-server restart
> --------------------------------------------------------------
>
> Key: AMBARI-8319
> URL: https://issues.apache.org/jira/browse/AMBARI-8319
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.7.0
> Reporter: Yusaku Sako
> Assignee: Yusaku Sako
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8319_branch-1.7.0.patch
>
>
> Updates to hdp-utils repo were not merged with default settings.
> The updates are stored in DB with key like:
> repo:/HDP/2.2/redhat6/HDP-UTILS-1.1.0.20:baseurl
> when reading from DB and merging the key was generated incorrectly:
> repo:/HDP-UTILS/2.2/redhat6/HDP-UTILS-1.1.0.20:baseurl
> so it used the stack name to store values and the repo name to retrieve.
> This worked for HDP (the same name for repo and stack) and did not work for
> HDP-UTILS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
