Body
Summary
After the distro upgrade (Ubuntu 22.04 → 24.04), the Imunify repo lists are correctly rewritten from .../ubuntu/22.04/... to .../ubuntu/24.04/... noble, but the signing key is not trusted under the upgraded system, so every Imunify repo fails apt's signature check. That poisons apt-get update, and stage 4 dies when /usr/local/cpanel/scripts/sysup cannot install its needed packages.
Environment
- cPanel & WHM v134.0.47, ELevate script version 83
- Ubuntu 22.04.5 → 24.04, ImunifyAV (free) installed pre-elevation
Evidence
W: GPG error: https://download.imunify360.com/ubuntu/24.04/slot-3 noble InRelease:
The following signatures couldn't be verified because the public key is not available:
NO_PUBKEY BC9A243190E02617
E: The repository 'https://download.imunify360.com/ubuntu/24.04/slot-3 noble InRelease' is not signed.
[... identical for every rollout slot ...]
(XID ...) "/usr/bin/apt-get" reported error code "100" when it ended:
E Sysup: Needed system packages were not installed: ea-cpanel-tools, ea-profiles-cpanel, libboost-program-options1.83.0, libpcap0.8t64
ELevate reports: "/usr/local/cpanel/scripts/sysup" failed. ... The elevation process failed during stage 4.
Workaround (verified)
Either import the CloudLinux key so the repos verify:
wget -qO- https://repo.imunify360.cloudlinux.com/defense360/RPM-GPG-KEY-CloudLinux \
| gpg --dearmor > /etc/apt/trusted.gpg.d/imunify360.gpg
or temporarily move the imunify*.list files out of /etc/apt/sources.list.d/ until the elevation completes. Then elevate-cpanel --continue proceeds normally (stage 4/5 completed for us after this).
Suggestion
Since ELevate already has Imunify-aware components, carrying the vendor key across the upgrade (or deferring the Imunify list re-enable until after sysup) would remove this failure. Possibly also worth reporting on the CloudLinux side — happy to do that if useful.
Body
Summary
After the distro upgrade (Ubuntu 22.04 → 24.04), the Imunify repo lists are correctly rewritten from
.../ubuntu/22.04/...to.../ubuntu/24.04/... noble, but the signing key is not trusted under the upgraded system, so every Imunify repo fails apt's signature check. That poisonsapt-get update, and stage 4 dies when/usr/local/cpanel/scripts/sysupcannot install its needed packages.Environment
Evidence
ELevate reports:
"/usr/local/cpanel/scripts/sysup" failed. ... The elevation process failed during stage 4.Workaround (verified)
Either import the CloudLinux key so the repos verify:
or temporarily move the
imunify*.listfiles out of/etc/apt/sources.list.d/until the elevation completes. Thenelevate-cpanel --continueproceeds normally (stage 4/5 completed for us after this).Suggestion
Since ELevate already has Imunify-aware components, carrying the vendor key across the upgrade (or deferring the Imunify list re-enable until after sysup) would remove this failure. Possibly also worth reporting on the CloudLinux side — happy to do that if useful.