[
https://issues.apache.org/jira/browse/AMBARI-11185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575368#comment-14575368
]
Hudson commented on AMBARI-11185:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2830 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2830/])
AMBARI-11185. Edit Repositories on an added repo version fails with 500 status
code. (Di Li via Jaimin) (jaimin:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8e496ce6114fd6ee0a8450ab9cbde6df68bbca1a)
* ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
*
ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js
* ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
> 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)
