-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
leapp upgrade fails with AttributeError: can't set attribute #173
Comments
Hello, If you review the leapp-upgrade.log, you can see that there is a package conflict with python36. A few others and myself have had this same problem. leapp does not do a good job of bringing this conflict to the users attention. Anyway, this is how i fixed the same issue.
|
Thanks for your quick response. Running I should probably have package conflict in the log. In my defence though, the file has over 24k lines! |
I wouldn't really blame yourself. It happened to me while upgrading a production server lol |
@beepmode you have two issues tagged as
The
I think you can fix it by removing your I think the second issue should not appear if you use the cpanel elevate script, if it does then please open a support ticket so we can access your server and investigate thanks |
@atoomic Just wanted to make you aware that the ticket i submitted to redhat bugzilla regarding the They essentially just kicked it back to cpanel / elevate / leapp, stating:
you can view the ticket here if you're so inclined. https://bugzilla.redhat.com/show_bug.cgi?id=2153539 as I also previously stated, it looks like the official leapp repo maintainers are aware of the conflict issues (and have been for awhile) as referenced in AlmaLinux/leapp-repository#22 and AlmaLinux/leapp-repository#15 but haven't taken any steps to fix it yet. |
thanks, I ve adjusted the link above. |
I am having the same issue with the same error message, but I do not have python36 installed on this system. |
It could be a different conflicting package. |
@danFbach thanks for the quick reply. My issue ended up being two items. The first one was several package conflicts not involving python36. Once those were removed then the Leapp upgrade finished without errors. The second issue was once the Leapp upgrade finished it only installed the kernel boot menu entry in the grub2-efi.cfg version. However, this VM didn't have UEFI enabled so it was using the Legacy BIOS grub2.cfg file during boot time. Once this entry was added it booted into the upgrade kernel and everything finished successfully. |
@Cassius242 you're welcome. Glad I could help and that you were able to complete the upgrade! |
If you have installed those packages from a repo, |
Glad your upgrade completed. We have created an internal case to block on python36 early so people do not experience this problem in the future. It should be released in a coming version of elevate-cpanel soon! |
#250 added to block on the presence of python36 which confuses leapp |
I keep running into the same error when running
leapp upgrade
. As far as I can tell this happens right after adnf update
command has completed.Known blockers check
Centos version (minimum is 7.9)
Available disk space:
cPanel version (minimum is 102)
Make sure system is up to date:
Current nameserver software (PowerDNS is recommended)
PHP version(s):
After reboot
leapp upgrade
then errors out after DNF updates have completed:I've attached the /var/log/leapp/leapp-report.txt file (the preflight check) and /var/log/leapp/leapp-upgrade.log. I can provide more information - just let me know what other info might be useful.
leapp-report.txt
leapp-upgrade.log
The text was updated successfully, but these errors were encountered: