[
https://issues.apache.org/jira/browse/AMBARI-11658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571449#comment-14571449
]
Hudson commented on AMBARI-11658:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2799 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2799/])
AMBARI-11658. Add Service Wizard resets local hdp repo to public repo
(onechiporenko) (onechiporenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=576796f76104b9b6d04322f72af85b0fc9a9d5b8)
* ambari-web/app/utils/ajax/ajax.js
* ambari-web/test/controllers/wizard/step8_test.js
* ambari-web/app/controllers/wizard/step8_controller.js
> Add Service Wizard resets local hdp repo to public repo
> -------------------------------------------------------
>
> Key: AMBARI-11658
> URL: https://issues.apache.org/jira/browse/AMBARI-11658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Fix For: 2.1.0
>
> Attachments: AMBARI-11658.patch
>
>
> PROBLEM: After upgrading to Ambari 2.0 and attempting to add services to the
> 2.2.4.2 cluster, the customer's HDP.repo keeps getting replaced with the
> default public repo.
> BUSINESS IMPACT: N/A
> STEPS TO REPRODUCE:
> 1. Browse to Admin>Stack and Versions>Versions
> 2. Edit current version
> 3. Modify one of the repositories to some other non-public URL (local or
> bogus: skip validation)
> 4. Check against (my edit was for redhat6) and confirm the changes are
> reflected.
> 5. Browse back to Services menu and launch Add Service Wizard
> 6. In the Review step of the wizard a list of repos is shown where all URL's
> are default public.
> 7. Moreover even if you modify the HDP.repo on the client hosts to reflect
> the local URL, the ASW overwrites that with the default public repo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
