Bug 1130219

Do we know the list of packages that are being grabbed from EPEL?

The RHEL OSP installer should not be enabling EPEL per default.

(In reply to Lon Hohberger from comment #3)
> The RHEL OSP installer should not be enabling EPEL per default.

Not sure how machines are provisioned but it is documented[1] to set yum priorities for RHOS repos, so RHOS should always win.
Please provide /etc/yum.repos.d/ folder.

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/5/html/Installation_and_Configuration_Guide/chap-Prerequisites.html#Red_Hat_OpenStack_Repository_Configuration

https://trello.com/c/Dmd7bKlx/84-need-epel-from-fedora-to-deploy-foreman

Can you please provide this information?  We won't enable EPEL by default.  Everything needed for RHEL-OSP installer should be included in RHN/CDN. 

(In reply to Lon Hohberger from comment #3)
> Do we know the list of packages that are being grabbed from EPEL?
> 
> The RHEL OSP installer should not be enabling EPEL per default.

This bug is related to the foreman_installer.sh script.   When the script runs, the script generates an epel.repo file in /etc/yum.repos.d which our network proxy blocks.  Thus we see the error shown below.   I originally assumed we needed the repo and modified the /usr/share/foreman-installer/modules/foreman/manifests/install/repos/extra.pp file to match our needs.  However, upon inspection, I just ran a test where I modified the extra.pp file by removing the generate_epel call line (second or third line in the file, if I recall correctly).  With this line removed, the foreman_installer.sh script does not generate the epel.repo file and appears to run fine. 


Notice: /Stage[main]/Foreman::Install::Repos::Extra/Yumrepo[epel]/ensure: created
Info: changing mode of /etc/yum.repos.d/epel.repo from 600 to 644
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list puppet-server' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
Error: /Stage[main]/Puppet::Server::Install/Package[puppet-server]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list puppet-server' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
Notice: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml]: Dependency Package[puppet-server] has failures: true
Warning: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml]: Skipping because of failed dependencies
Notice: /Stage[main]/Foreman_proxy::Proxydns/Dns::Zone[121.168.192.in-addr.arpa]/Concat_fragment[dns_zones+10_121.168.192.in-addr.arpa.dns]/content: content changed '' to 'zone "121.168.192.in-addr.arpa" {
    type master;
    file "/var/named/dynamic/db.121.168.192.in-addr.arpa";
    update-policy {
            grant rndc-key zonesub ANY;
    };
};
'
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-proxy' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
Error: /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-proxy' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again.

This bug is related to the foreman_installer.sh script.   When the script runs, the script generates an epel.repo file in /etc/yum.repos.d which our network proxy blocks.  Thus we see the error shown below.   I originally assumed we needed the repo and modified the /usr/share/foreman-installer/modules/foreman/manifests/install/repos/extra.pp file to match our needs.  However, upon inspection, I just ran a test where I modified the extra.pp file by removing the generate_epel call line (second or third line in the file, if I recall correctly).  With this line removed, the foreman_installer.sh script does not generate the epel.repo file and appears to run fine. 


Notice: /Stage[main]/Foreman::Install::Repos::Extra/Yumrepo[epel]/ensure: created
Info: changing mode of /etc/yum.repos.d/epel.repo from 600 to 644
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list puppet-server' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
Error: /Stage[main]/Puppet::Server::Install/Package[puppet-server]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list puppet-server' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
Notice: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml]: Dependency Package[puppet-server] has failures: true
Warning: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml]: Skipping because of failed dependencies
Notice: /Stage[main]/Foreman_proxy::Proxydns/Dns::Zone[121.168.192.in-addr.arpa]/Concat_fragment[dns_zones+10_121.168.192.in-addr.arpa.dns]/content: content changed '' to 'zone "121.168.192.in-addr.arpa" {
    type master;
    file "/var/named/dynamic/db.121.168.192.in-addr.arpa";
    update-policy {
            grant rndc-key zonesub ANY;
    };
};
'
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-proxy' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again
Error: /Stage[main]/Foreman_proxy::Install/Package[foreman-proxy]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y list foreman-proxy' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: epel. Please verify its path and try again.

*** Bug 1130215 has been marked as a duplicate of this bug. ***

The fix for this bug has been verified by JT in the 9/12 puddle.

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.

http://rhn.redhat.com/errata/RHBA-2014-1350.html