[
https://issues.apache.org/jira/browse/AMBARI-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565694#comment-14565694
]
Hadoop QA commented on AMBARI-11185:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12736191/AMBARI-11185.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 2 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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2931//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2931//console
This message is automatically generated.
> Edit Repositories on an added repo version fails with 500 status code
> ---------------------------------------------------------------------
>
> Key: AMBARI-11185
> URL: https://issues.apache.org/jira/browse/AMBARI-11185
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Di Li
> Assignee: Di Li
> Fix For: 2.1.0
>
> Attachments: AMBARI-11185.patch, err-1.png
>
>
> I used HDP beta build:
> http://s3.amazonaws.com/dev.hortonworks.com/ambari/centos6/2.x/BUILDS/2.1.0-630
> On the Stack and Versions page, under Versions tab, user cannot update the
> repo URL of an added Repo version. Users can add repo versions via the
> "Manage Versions" button, however after the repo is added, user cannot update
> the repo URL anymore.
> As part of the update repo URL feature introduced in Ambari 2.0, a repo
> version check was added to make sure the repo added has the same version info
> as the one installed, due to Ambari 2.0 's rolling upgrade limitations.
> In the Ambari 2.1 build I tried, the repo version check
> (AmbariManagementControllerImpl.verifyRepository) is still the Ambari 2.0
> behavior where it rejects any updates of HDP 2.3 repo URL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
