[
https://issues.apache.org/jira/browse/AMBARI-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241484#comment-14241484
]
Hudson commented on AMBARI-8639:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #1162 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1162/])
AMBARI-8639. Distribute Repository/Install: parallel install not working
(dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b60f26ee9a3ae20a37e49f0158e581862643ef86)
* ambari-common/src/main/python/resource_management/core/resources/packaging.py
*
ambari-common/src/main/python/resource_management/core/providers/package/zypper.py
*
ambari-common/src/main/python/resource_management/core/providers/package/apt.py
* ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
*
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
*
ambari-common/src/main/python/resource_management/core/providers/package/__init__.py
* ambari-agent/src/test/python/resource_management/TestPackageResource.py
* ambari-server/src/test/python/custom_actions/TestInstallPackages.py
*
ambari-server/src/test/python/custom_actions/configs/install_packages_config.json
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java
> Distribute Repository/Install: parallel install not working
> -----------------------------------------------------------
>
> Key: AMBARI-8639
> URL: https://issues.apache.org/jira/browse/AMBARI-8639
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8639.patch
>
>
> As of Dec 9.
> * Installed a brand new cluster from trunk.
> * Installed initial repository with no issue of 2.2.0.0-2041.
> * This created repo files HDP.repo and HDP-UTILS.repo on each host.
> * All green.
> Then, attempted creation of a new version. Custom Action invoked
> successfully, but the result failed.
> 1. For HDP, ended up with two files: HDP.repo and HDP-2.2.repo. Each file
> contained a repo named "HDP-2.2". The output of the yum invokation contains:
> {noformat}
> 2014-12-09 19:19:54,929 - Package['zookeeper_2_2_*'] {}
> 2014-12-09 19:19:55,300 - Skipping installing existent package zookeeper_2_2_*
> {noformat}
> which should definitely NOT happen.
> 2. The name of the repository file should be a little more specific. There
> may be several "HDP-2.2" that a cluster is upgraded to.
> 3. The installation should use ONLY the repo designated that it just
> created, such that we know that the version installed is from the correct
> repo. The command should be something like: {{yum install --disablerepo=*
> --enablerepo="HDP-2.2.0.0-1234" zookeeper_2_2_*}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
