-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Actor dnf_package_download unexpectedly terminated #15
Comments
Let's try to all EPEL support to your configuration. epel_map.json
epel_pes.json
epel.repo
epel.sigs
Then do as usual:
|
Same result: ==================================================================================
|
1 similar comment
Same result: ==================================================================================
|
Same problem trying to upgrade from CentOS 7 to AlmaLinux 8 using elevate-cpanel
|
I get the same error trying to upgrade from CentOS7 to Rocky. |
Same problem here on six different machines, but another four machines with similar configurations are fine. Removing all epel packages (and all systems have one or two) and then re-running leapp upgrade does not help. Any idea at all what is going on or if there is any kind of upgrade? In our case it appears to have done all the downloads before this happens so if we could just bypass the rest of the module and go to the next one we might even be okay. |
The issue might be with the old python installation. Try removing python2* and python3* packages and then try again. |
Pardon the formatting, I had hard time to include info in details tags. Once I updated the leapp to latest 0.14 I have same issue on centos 7.9.
root@centos7t01 ~]# rpm -qa |grep leapp
leapp-0.12.1-100.20210924142320684911.master.28.g1f03432.el7.noarch
python2-leapp-0.12.1-100.20210924142320684911.master.28.g1f03432.el7.noarch
leapp-deps-0.12.1-100.20210924142320684911.master.28.g1f03432.el7.noarch
leapp-upgrade-el7toel8-0.14.0-100.202109271224Z.b7ebfca.master.el7.elevate.noarch
leapp-data-rocky-0.1-4.el7.noarch
leapp-upgrade-el7toel8-deps-0.14.0-100.202109271224Z.b7ebfca.master.el7.elevate.noarch
[root@centos7t01 ~]#
installing package nss-softokn-freebl-3.79.0-10.el8_6.i686 needs 2728MB on the / filesystem Error SummaryDisk Requirements: Debug output written to /var/log/leapp/leapp-upgrade.log Adding epel* in /etc/leapp/files/vendors.d/ fix didn't fix the issue. 2022-11-26 11:57:20.313 DEBUG PID: 10582 leapp.workflow.Download.dnf_package_download: Cleaning up mounts Answerfile has been generated at /var/log/leapp/answerfile
|
My issue was related to "disk space" so I increased the size and the other one was related to an openssl lib which was only el7 and I had to remove first. |
@MarcelRei , what version of leapp were you using when ran into disk pace issue ? |
I create a centos 7.9 VMWare VM from CentOS-7-x86_64-Minimal-2009 with no extra software installation beside leapp*.
|
I was using leapp 0.14 but still ran into the issue mentioned above. I just checked the logs better to find the issue. |
disk space issue still exists in 0.14 version. Thanks for this infomation. |
What is happening here is that the error handler is crashing and that is the message that we are seeing. So there could be all kinds of different errors occurring but we see the same error message for all of them.
I have found that a workaround is to look at /var/log/leapp/leapp-upgrade.log, or for preupgrade, the leapp-preupgrade.log. Start at the bottom, go from the syntax error up through all of the dismount and cleanup stuff and you will, maybe 50 lines from the end, find some kind of actual error message. It is sometimes hidden but it's likely to be there.
And yes, if you have an xfs filesystem, you need to increase LEAPP_OVL_SIZE. I have found I have needed to crank it up as high as 8192 on some systems with large xfs arrays.
But the real problem of the error handler crashing really needs to be addressed by the developers.
--scott
…________________________________
From: T.J. Yang ***@***.***>
Sent: Monday, November 28, 2022 6:21 AM
To: AlmaLinux/leapp-repository ***@***.***>
Cc: Dorsey, Scott B. (LARC-D316)[AEGIS] ***@***.***>; Comment ***@***.***>
Subject: [EXTERNAL] Re: [AlmaLinux/leapp-repository] Actor dnf_package_download unexpectedly terminated (Issue #15)
My issue was related to "disk space" so I increased the size export LEAPP_OVL_SIZE=3000
and the other one was related to an openssl lib which was only el7 and I had to remove first.
@MarcelRei<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMarcelRei&data=05%7C01%7Cscott.b.dorsey%40nasa.gov%7C17592b304c6d4fb8ab4e08dad132a824%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638052312757900245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1eah2TkFdtJVVSbh4oVSqlrycEX6mH9ZCkDH6lBo6Ns%3D&reserved=0> , what version of leapp were you using when ran into disk pace issue ? 0.12 or 0.14 ?
I was using leapp 0.14 but still ran into the issue mentioned above. I just checked the logs better to find the issue.
disk space issue still exists in 0.14 version. Thanks for this infomation.
—
Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAlmaLinux%2Fleapp-repository%2Fissues%2F15%23issuecomment-1328913052&data=05%7C01%7Cscott.b.dorsey%40nasa.gov%7C17592b304c6d4fb8ab4e08dad132a824%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638052312757900245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SawT1ZttRY6c%2F%2FQuv%2FZ%2F19Yp9PIwIT9KebGdn9W6tK4%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAS4OMCWK65UTMLMJIIPS22TWKSISLANCNFSM6AAAAAARC6X6PE&data=05%7C01%7Cscott.b.dorsey%40nasa.gov%7C17592b304c6d4fb8ab4e08dad132a824%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638052312757900245%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pkHOnuDklPs2jmPdXh9eeIWFM9s3%2B51dIjSP9vEdteo%3D&reserved=0>.
You are receiving this because you commented.Message ID: ***@***.***>
|
This ended up being my issue.
Thanks! This is how I found out what the exact issue was. Turned out to be a python library incompatibility and it was buried in that log file. |
My understanding so far for solution.
|
I'm curious if the logic of |
I would agree with this. If package conflicts can be removed automatically, remove them. If not, at least better inform the user. I, and others, have encountered this issue, that were all resolved by removing conflicting packages.
However, no information is given immediately to the user that this occurred because of conflicting packages, and one must dig into leapp-upgrade.log in order to find the information. For me and many others, it was python conflicts, but i've seen it occur with other packages. |
There are many things which can fail in the upgrade process. I have had all kinds of different errors, including package conflicts but also simple things like not having LEAPP_OVL_SIZE set. If you have shotwell installed, it gets confused because it wants to replace shotwell with gnome-photos and it can't find gnome-photos. All kinds of things can go wrong in the process.
The number one problem is that the error handler is broken. The user often cannot figure out what has gone wrong because the error handler is broken.
It would be good long-term to make fewer things go wrong, but FIRST fix the error handler.
--scott
…________________________________
From: Dan Fehrenbach ***@***.***>
Sent: Friday, December 30, 2022 1:38 PM
To: AlmaLinux/leapp-repository ***@***.***>
Cc: Dorsey, Scott B. (LARC-D316)[AEGIS] ***@***.***>; Comment ***@***.***>
Subject: [EXTERNAL] Re: [AlmaLinux/leapp-repository] Actor dnf_package_download unexpectedly terminated (Issue #15)
* remove pkg conflicts in advance
I'm curious if the logic of dnf system-upgrade download could possibly help here. Or at least showing the package conflict errors in stderr rather than buried in the log file.
I would agree with this. If package conflicts can be removed automatically, remove them. If not, at least better inform the user. I, and others, have encountered this issue, that were all resolved by removing conflicting packages.
The common reported error seems to be:
Risk Factor: high
Title: Packages from unknown repositories may not be installed
Summary: 1 packages may not be installed or upgraded due to repositories unknown to leapp:
- kernel-uek (repoid: ol8-uek)
However, no information is given immediately to the user that this occurred because of conflicting packages, and one must dig into leapp-upgrade.log in order to find the information. For me and many others, it was python conflicts, but i've seen it occur with other packages.
—
Reply to this email directly, view it on GitHub<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAlmaLinux%2Fleapp-repository%2Fissues%2F15%23issuecomment-1368046730&data=05%7C01%7Cscott.b.dorsey%40nasa.gov%7C1210058240f54b2dfa0d08daea95187e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638080223345861966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qonqOKDeEMULNbqhmYh8PQOZX1gUahIt6I1QvtZevkM%3D&reserved=0>, or unsubscribe<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAS4OMCT56E3CRUOWGC26I23WP4T3PANCNFSM6AAAAAARC6X6PE&data=05%7C01%7Cscott.b.dorsey%40nasa.gov%7C1210058240f54b2dfa0d08daea95187e%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C638080223345861966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=A89Mcrq54Mv9qmNNpRkgD%2BGP0275%2BVt7uVVRwJ8Wldk%3D&reserved=0>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Actual behavior
The migration from CentOS 7 to Rocky Linux 8 fails with error:
The text was updated successfully, but these errors were encountered: