In July of 2025 Plesk pushed out an unauthorized automated install of the Imunify 360 software. This situation lasted a few hours, but was long enough to affect hundreds of my systems that did check-ins during the time in question. Plesk and Imunify never automated a complete removal of the software on the affected systems, so even if you had executed the plesk installer extension removal via plesk bin extension --uninstall imunify360 at the time, it left behind numerous remnants, which include the yum repo definitions.
On systems where this was not properly cleaned up, it appears to be able to cause a conversion failure:
2026-06-23 17:37:47,901 - DEBUG - Invoking action 'fetching Imunify360 GPG key'
2026-06-23 17:37:47,901 - INFO - Do: fetching Imunify360 GPG key
2026-06-23 17:37:47,901 - DEBUG - Going to save GPG key from 'file:///usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux' to '/etc/leapp/files/vendors.d/rpm-gpg/RPM-GPG-KEY-CloudLinux'
2026-06-23 17:37:47,903 - ERROR - Error occurred while fetching GPG key from 'file:///usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux': <urlopen error [Errno 2] No such file or directory: '/usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux'>
2026-06-23 17:37:47,914 - DEBUG - Disable systemd 'plesk-dist-upgrade-resume.service' service after conversion failure
2026-06-23 17:37:47,922 - INFO - Running: ['/usr/bin/systemctl', 'disable', 'plesk-dist-upgrade-resume.service']. Output:
2026-06-23 17:37:47,930 - INFO - stderr: Removed /etc/systemd/system/multi-user.target.wants/plesk-dist-upgrade-resume.service.
2026-06-23 17:37:48,547 - INFO - Command ['/usr/bin/systemctl', 'disable', 'plesk-dist-upgrade-resume.service'] finished successfully
2026-06-23 17:37:48,547 - ERROR - Failed: fetching Imunify360 GPG key. The reason: Unable to fetch GPG key from 'file:///usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux': <urlopen error [Errno 2] No such file or directory: '/usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux'>. To continue with the conversion,please manually install the key into '/etc/leapp/files/vendors.d/rpm-gpg'.
2026-06-23 17:37:48,680 - DEBUG - Going to write json '/usr/local/psa/var/almalinux8to9/actions.json' with new data
2026-06-23 17:37:49,508 - DEBUG - Sent error report
2026-06-23 17:37:49,518 - DEBUG - Trying to send status of conversion by report-update utility '/root/parallels/report-update'
2026-06-23 17:37:50,323 - ERROR - almalinux8to9 process has failed. Error: Failed: fetching Imunify360 GPG key. The reason: Unable to fetch GPG key from 'file:///usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux': <urlopen error [Errno 2] No such file or directory: '/usr/share/imunify-pki/rpm-gpg/RPM-GPG-KEY-CloudLinux'>. To continue with the conversion,please manually install the key into '/etc/leapp/files/vendors.d/rpm-gpg'.
Unrelated to the conversion, but for those affected by the same issue who happen across this post, the proper full removal of this software looks like:
plesk bin extension --uninstall imunify360
systemctl disable imunify-notifier.service imunify-notifier.socket imunify-antivirus-sensor.socket imunify-antivirus-user.socket imunify-antivirus.socket
chattr -i /opt/ai-bolit
chattr -i /opt/ai-bolit/*
rm -rf /opt/ai-bolit
rm -rf /opt/i360_pam_imunify/
rm -rf /opt/imunify360
rm -rf /opt/imunify360-webshield
rm -f /etc/yum.repos.d/imunify360*
rm -rf /usr/share/imunify360
rm -rf /var/log/imunify360
rm -rf /var/log/i360deploy.log
rm -rf /var/log/imav-deploy.log
rm -rf /var/log/imunify360-webshield/
rm -rf /var/log/i360deploy-plesk.log
rm -rf /var/imunify360
rm -rf /var/i360_pam_imunify/
rm -rf /var/cache/yum/x86_64/7/imunify360*
rm -rf /var/lib/yum/repos/x86_64/7/imunify360*
rm -f /var/www/vhosts/*/.imunify_patch_id
rm -f /etc/cron.daily/imunify360-ossec-server
rm -f /etc/cron.d/imunify-antivirus
rm -f /etc/cron.d/imunify-notifier
rm -f /etc/crond.d/i360_pkg_watcher
rm -f /etc/sysconfig/aibolit-resident
rm -rf /etc/imunify360/
rm -rf /etc/imunify360-wafd/
rm -rf /etc/imunify360-webshield/
rm -rf /etc/imunify-realtime-av/
rm -rf /etc/sysconfig/imunify360
rm -f /etc/apt/sources.list.d/imunify*
rm -f /etc/systemd/system/imunify-notifier.service
rm -f /etc/systemd/system/imunify-notifier.socket
rm -f /etc/systemd/system/multi-user.target.wants/imunify-notifier.service
rm -f /etc/systemd/system/sockets.target.wants/imunify-notifier.socket
rm -f /etc/systemd/system/sockets.target.wants/imunify-antivirus-*.socket
rm -rf /var/lib/systemd/deb-systemd-helper-enabled/*imunify*
rm -rf /var/lib/systemd/deb-systemd-helper-masked/*imunify*
rm -rf /var/lib/imunify360-php-daemon
rm -rf /var/lib/apt/lists/*imunify*
rm -rf /var/lib/dpkg/info/imunify*
rm -rf /var/lib/imunify360-php-daemon
rm -rf /var/lib/systemd/deb-systemd-helper-enabled/imunify*
rm -rf /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/imunify-notifier.service
rm -rf /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/imunify-notifier.socket
userdel _imunify
userdel imunify360-webshield
groupdel _imunify
In July of 2025 Plesk pushed out an unauthorized automated install of the Imunify 360 software. This situation lasted a few hours, but was long enough to affect hundreds of my systems that did check-ins during the time in question. Plesk and Imunify never automated a complete removal of the software on the affected systems, so even if you had executed the plesk installer extension removal via
plesk bin extension --uninstall imunify360at the time, it left behind numerous remnants, which include the yum repo definitions.On systems where this was not properly cleaned up, it appears to be able to cause a conversion failure:
Unrelated to the conversion, but for those affected by the same issue who happen across this post, the proper full removal of this software looks like: