kaltura / platform-install-packages

Official deployment packages to install the Kaltura platform on a server or cluster environments using native OS package managers
GNU Affero General Public License v3.0
520 stars 242 forks source link

Vagrant setup broken due to EPEL for RHEL/CentOS 6 no longer available #703

Open edalex-ian opened 3 years ago

edalex-ian commented 3 years ago

Bug report

As you'll see from my other recent issues (#701 and #702) I've been trying every possible way to get Kaltura setup and running locally for some dev work to update the openEQUELLA support for Kaltura. However as well as issues using the pre-build Docker image and attempting a manual install on Debian, there is also an issue with the Vagrant setup. (Which mind you, would also be an issue attempting to rebuild the Dockerfile.)

On line 12 of vagrant/kaltura-install.sh and attempt is made to retrieve the EPEL for RHEL/CentOS 6. However I guess with RHEL/CentOS 6 now being so old this results in:

    default: Retrieving https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm
    default: 35) SSL connect error
    default: error: skipping https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm - transfer failed
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

This was also checked with simple wget directly:

$ wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm
--2021-05-20 12:47:07--  https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm
Resolving dl.fedoraproject.org (dl.fedoraproject.org)... 38.145.60.22, 38.145.60.23, 38.145.60.24
Connecting to dl.fedoraproject.org (dl.fedoraproject.org)|38.145.60.22|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2021-05-20 12:47:09 ERROR 403: Forbidden.

And when reading the EPEL wiki page I note they now only provide links for 7 and 8 - which I confirmed work.

So it looks like both the Dockerfile and the Vagrant setup need to be updated to CentOS 8 - or at least 7.