Description of problem: The HDP plugin installs EPEL as part of its installation flow. Providing that a generated image is used, nothing is installed from this repository, but failure to install it or read its metadata will result in a failed cluster. Empirical tests verify that this installation can be wholly removed. How reproducible: 100% (cluster creation failure is extremely sporadic, but package installation is universal.) Steps to Reproduce: 1. Create any cluster using the HDP plugin. 2. Await cluster 'active' state. 3. Verify that 'epel.repo' exists in /etc/yum.repos.d/ on any cluster node. Actual results: EPEL repo exists on cluster nodes (though a yum list reveals that no package is installed from this repo.) Expected results: EPEL is uninstalled on RHEL HDP cluster nodes. Additional info: See https://bugzilla.redhat.com/show_bug.cgi?id=1221881
After this change, the instances of RHEL6 started by Sahara to build an HDP 2.0.6 cluster do not have the epel repositories enabled. Verified with: openstack-sahara-2014.2.3-3.el7ost.noarch python-saharaclient-0.7.6-1.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1659.html