Latest Installer fails due to 403 status for Powertools

[JohnnyViking]

New server and trying to install on a clean CentOS 8 server.

Getting this error:

2021-09-13 10:11:45 350 [10237] (DEBUG): - ssystem [BEGIN]: /usr/bin/yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm --enablerepo=powertools
2021-09-13 10:11:45 350 [10237] (DEBUG): Last metadata expiration check: 0:00:10 ago on Mon Sep 13 10:11:35 2021.
2021-09-13 10:11:46 350 [10237] (DEBUG): [MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
2021-09-13 10:11:46 350 [10237] (DEBUG): [MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
2021-09-13 10:11:46 350 [10237] (DEBUG): [MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
2021-09-13 10:11:46 350 [10237] (DEBUG): [MIRROR] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
2021-09-13 10:11:46 350 [10237] (DEBUG): [FAILED] epel-release-latest-8.noarch.rpm: Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
2021-09-13 10:11:46 350 [10237] (DEBUG): Status code: 403 for https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm (IP: 38.145.60.22)
2021-09-13 10:11:46 350 [10237] (ERROR): - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored)
2021-09-13 10:11:46 350 [10237] (DEBUG): - ssystem [END]
2021-09-13 10:11:46 354 [10237] (FATAL): yum failed 6 times. The installation process cannot continue.

Googling this I found another thread from last year and it seems you need to correct this in the installer script.

There simply is nothing on the URL that the installer tries to fetch Powertools from.

 

[cPJustinD]

Hello there! We did see some reports of the error previously, although we've seen instances where trying after a few hours allows the install to complete. It's currently unclear what exactly is occurring.

I think it would be best to open a support ticket so that our analysts can review the issue more thoroughly and determine what exactly is occurring. You can submit a support request using the "Submit a ticket" link in my signature below.

Please be sure to link this thread when opening the ticket and provide the ticket number here so that we can track the issue appropriately. If possible, please post the resolution on this thread as it may help other community members with similar issues.