From 03e177e58bf9928dd0e4916575cb3ea803d3bd4c Mon Sep 17 00:00:00 2001 From: Steve Kuznetsov Date: Mon, 13 Feb 2017 10:24:16 -0500 Subject: [PATCH] Install EPEL using the `epel-release` package Instead of pinning the EPEL installation to a specific RPM and version from a download, we should install EPEL using the `epel-release` package available in `yum`. Signed-off-by: Steve Kuznetsov --- lib/vagrant-openshift/action/create_yum_repositories.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/vagrant-openshift/action/create_yum_repositories.rb b/lib/vagrant-openshift/action/create_yum_repositories.rb index 57901829..ad98790b 100644 --- a/lib/vagrant-openshift/action/create_yum_repositories.rb +++ b/lib/vagrant-openshift/action/create_yum_repositories.rb @@ -55,7 +55,7 @@ def call(env) unless is_fedora unless env[:machine].communicate.test("rpm -q epel-release") - sudo(env[:machine], "yum install -y http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-8.noarch.rpm") + sudo(env[:machine], "yum install -y epel-release") #Workaround broken RHEL image which does not recover after restart. if "VagrantPlugins::AWS::Provider" == env[:machine].provider.class.to_s