In Progress CPANEL-42738 - cPanel ELevate - unsupported YUM repo

BassTeQ · Aug 15, 2023

Hello,

I'm seeing the below errors in elevate-cpanel.log. Will this be an issue when trying to update to Almalinux?
They look to be related to CentOS system components.

Code:

264 package(s) installed from unsupported YUM repo 'system-base' from /etc/yum.repos.d/yum.system.repo
55 package(s) installed from unsupported YUM repo 'system-updates-released' from /etc/yum.repos.d/yum.system.repo
Unsupported YUM repo enabled 'system-extras' without packages installed from /etc/yum.repos.d/yum.system.repo, these will be disabled before ELevation
4 package(s) installed from unsupported YUM repo 'stable-generic' from /etc/yum.repos.d/yum.sourcedns.repo
11 package(s) installed from unsupported YUM repo 'stable-arch' from /etc/yum.repos.d/yum.sourcedns.repo
10 package(s) installed from unsupported YUM repo 'stable-noarch' from /etc/yum.repos.d/yum.sourcedns.repo
*** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

/etc/yum.repos.d/yum.system.repo

Code:

name=CentOS-$releasever - $basearch - Base (Production system packages)
baseurl=http://syspackages.sourcedns.com/packages/mirrors/centos/7/os/$basearch/
gpgcheck=1
priority=3

[system-updates-released]
name=CentOS-$releasever - $basearch - Released Updates (Production system packages)
baseurl=http://syspackages.sourcedns.com/packages/mirrors/centos/7/updates/$basearch/
gpgcheck=1
priority=3

[system-extras]
name=CentOS-$releasever - $basearch - Extras (Production system packages)
baseurl=http://syspackages.sourcedns.com/packages/mirrors/centos/7/extras/$basearch/
gpgcheck=1
priority=3

/etc/yum.repos.d/yum.sourcedns.repo

Code:

[stable-generic]
name= Stable Generic Packages
baseurl=http://syspackages.sourcedns.com/packages/stable/generic/noarch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/packages.pub.key
priority=2

[stable-arch]
name= Stable Arch Specific Packages
baseurl=http://syspackages.sourcedns.com/packages/stable/centos/7/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/packages.pub.key
priority=2

[stable-noarch]
name= Stable Distro Specific Non-Architecture Specific Packages
baseurl=http://syspackages.sourcedns.com/packages/stable/centos/7/noarch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/packages.pub.key
priority=2

Thanks

cPRex · Aug 16, 2023

Hey there! Yes, anything that triggers the "Elevation Blocker Detected" output will cause the update to fail, and needs to be resolved before the upgrade is attempted.

BassTeQ · Aug 17, 2023

Thanks, so anything in the below repo's are not reqired by cPanel specifically?

system-base
system-updates-released
stable-generic
stable-arch
stable-noarch

Looking at whats installled in 'stable-noarch', I see some cPanel packages, woudn't these be required?

Code:

cpanel-api2-wordpress-staging-sites.noarch   0.0.3-0.el7.centos     @stable-noarch
cpanel-api2-wpcli.noarch                  0.0.1-6.el7.centos       @stable-noarch

cPRex · Aug 17, 2023

No, all of those repos and packages are normal. The "system-extras" repository is the one causing conflict, as well as certain packages from the yum.sourcedns.repo. However, "sourcedns" is GoDaddy, so you may need to speak with them to determine what is necessary for the server and if your specific environment is even cable of using the ELevate tool.

BassTeQ · Aug 17, 2023

Thanks, my server is with liquidweb, and I've discovered what looks like the same issue I'm having was raised on the github 12 months ago https://github.com/cpanel/elevate/issues/121 and it's still not been resolved.

cPRex · Aug 18, 2023

Thanks for commenting on that case. I also let the ELevate team know and if I hear anything on my end I'll let you know!

cPRex · Aug 18, 2023

Even though that case isn't resolved, you can still remove the RPMs in order to ELevate. You just may need to check with your host to ensure removing those specific packages won't cause data loss.

mtindor · Aug 18, 2023

cPRex said:
No, all of those repos and packages are normal. The "system-extras" repository is the one causing conflict, as well as certain packages from the yum.sourcedns.repo. However, "sourcedns" is GoDaddy, so you may need to speak with them to determine what is necessary for the server and if your specific environment is even cable of using the ELevate tool.

SourceDNS is GoDaddy? Those repos end up getting installed on my LiquidWeb servers and I believe have something to do with packages. Never had a server at GoDaddy. I am not having any issues. I'm just chiming in because I think that LiquidWeb customers would see those sourcedns repos too.

cPRex · Aug 18, 2023

Ah, Liquid Web is what I was thinking! Not GoDaddy.

BassTeQ · Aug 20, 2023

cPRex said:
Thanks for commenting on that case. I also let the ELevate team know and if I hear anything on my end I'll let you know!

Thank you very much! I'll also contact liquidweb and confrm of those modules can be removed.

cPRex said:
No, all of those repos and packages are normal. The "system-extras" repository is the one causing conflict, as well as certain packages from the yum.sourcedns.repo.

I've disabled system-extras now, and the elevate log is still showing the below as blockers. You'd mentioned yum.sourcedns.repo will be an issue, however it still includes yum.system.repo so I'm a little confused.

Code:

264 package(s) installed from unsupported YUM repo 'system-base' from /etc/yum.repos.d/yum.system.repo
55 package(s) installed from unsupported YUM repo 'system-updates-released' from /etc/yum.repos.d/yum.system.repo
4 package(s) installed from unsupported YUM repo 'stable-generic' from /etc/yum.repos.d/yum.sourcedns.repo
11 package(s) installed from unsupported YUM repo 'stable-arch' from /etc/yum.repos.d/yum.sourcedns.repo
10 package(s) installed from unsupported YUM repo 'stable-noarch' from /etc/yum.repos.d/yum.sourcedns.repo
*** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them before continuing the update.

Thanks

cPRex · Aug 21, 2023

That final output is just letting you know the packages exist. There should be other information in the log before that to show what the specific blockers are.

BassTeQ · Aug 21, 2023

Here's the full log /var/log/elevate-cpanel.log

Code:

* 2023-08-21 04:29:46 (1700) [^[[32mINFO^[[0m] Checking if your system is up to date:
* 2023-08-21 04:29:46 (4088) [^[[32mINFO^[[0m] Running: /usr/bin/yum clean all
* 2023-08-21 04:29:46 (4089) [^[[32mINFO^[[0m]
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m] Loaded plugins: fastestmirror, priorities, universal-hooks
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB103
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m]               : imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m]               : stable-arch stable-generic stable-noarch system-base
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m]               : system-updates-released wp-toolkit-cpanel
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m]               : wp-toolkit-thirdparties
* 2023-08-21 04:29:46 (4102) [^[[32mINFO^[[0m] Other repos take up 7.0 M of disk space (use --verbose for details)
* 2023-08-21 04:29:46 (4119) [^[[32mINFO^[[0m]
* 2023-08-21 04:29:46 (4088) [^[[32mINFO^[[0m] Running: /usr/bin/yum check-update -q
* 2023-08-21 04:29:46 (4089) [^[[32mINFO^[[0m]
* 2023-08-21 04:30:07 (4119) [^[[32mINFO^[[0m]
* 2023-08-21 04:30:07 (1721) [^[[32mINFO^[[0m] Checking /scripts/sysup
* 2023-08-21 04:30:07 (4088) [^[[32mINFO^[[0m] Running: /scripts/sysup
* 2023-08-21 04:30:07 (4089) [^[[32mINFO^[[0m]
* 2023-08-21 04:30:07 (4102) [^[[32mINFO^[[0m] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-21 04:30:08 (4102) [^[[32mINFO^[[0m]   All Needed Packages are already installed.
* 2023-08-21 04:30:08 (4119) [^[[32mINFO^[[0m]
* 2023-08-21 04:30:10 (1625) [^[[31mERROR^[[0m] 264 package(s) installed from unsupported YUM repo 'system-base' from /etc/yum.repos.d/yum.system.repo
* 2023-08-21 04:30:10 (1625) [^[[31mERROR^[[0m] 55 package(s) installed from unsupported YUM repo 'system-updates-released' from /etc/yum.repos.d/yum.system.repo
* 2023-08-21 04:30:10 (1625) [^[[31mERROR^[[0m] 4 package(s) installed from unsupported YUM repo 'stable-generic' from /etc/yum.repos.d/yum.sourcedns.repo
* 2023-08-21 04:30:10 (1625) [^[[31mERROR^[[0m] 11 package(s) installed from unsupported YUM repo 'stable-arch' from /etc/yum.repos.d/yum.sourcedns.repo
* 2023-08-21 04:30:10 (1625) [^[[31mERROR^[[0m] 10 package(s) installed from unsupported YUM repo 'stable-noarch' from /etc/yum.repos.d/yum.sourcedns.repo
* 2023-08-21 04:30:10 (153) [^[[33mWARN^[[0m] *** Elevation Blocker detected: ***
One or more enabled YUM repo are currently unsupported and have installed packages.
You should disable these repositories and remove packages installed from them
before continuing the update.

* 2023-08-21 04:30:27 (778) [^[[32mINFO^[[0m] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-21 04:30:27 (2236) [^[[32mINFO^[[0m] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dDMLGBEDCN/ea_profile.json
* 2023-08-21 04:30:28 (2259) [^[[32mINFO^[[0m] Backed up EA4 profile to /tmp/dDMLGBEDCN/ea_profile.json
* 2023-08-21 04:30:30 (258) [^[[33mWARN^[[0m] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/

cPRex · Aug 22, 2023

Thanks for providing that, although that log doesn't seem very helpful. I'd recommend submitting a ticket to our team so we can look into this for you.

BassTeQ · Aug 22, 2023

Sure will do, thanks!

cPRex · Aug 23, 2023

If you're able to do that, can you post the ticket number here so I can follow along?

BassTeQ · Aug 23, 2023

cPRex said:
If you're able to do that, can you post the ticket number here so I can follow along?

Sure, it's 95111582
Thanks

cPRex · Aug 24, 2023

I see we were able to determine this is related to CPANEL-42738, and our team is working on that case now. I'll be sure to post an update here if I hear anything.

BassTeQ · Aug 24, 2023

Thanks very much!

cPRex · Aug 28, 2023

Sure thing!

BassTeQ · Sep 17, 2023

cPRex said:
Sure thing!

Hi, just checking if there has there been any update on CPANEL-42738 ?

Cheers

Thread starter	Similar threads	Forum	Replies	Date
	Permission denied at /usr/local/cpanel/Cpanel/Config/userdata/Load.pm line 82.	Server Management	3	Monday at 1:58 AM
S	CPanel Server Services Down After Migration and Reboot	Server Management	1	Nov 23, 2023
R	Installing an old version of Cpanel	Server Management	6	Nov 22, 2023
P	Enable ionCube AlmaLinux 8 and cPanel 114.0.12	Server Management	2	Nov 18, 2023
D	Possible memory leak in cpanel backup service	Server Management	4	Nov 15, 2023

In Progress CPANEL-42738 - cPanel ELevate - unsupported YUM repo

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member

Jurassic Moderator

Well-Known Member