Closed LielZ closed 1 year ago
Thanks for reporting this issue. I can see multiple Risk Factor: high
.
We are going to investigate all of these issues. But here is a quick feedback:
Issue 1: leapp itself does not know how to upgrade kernel-uek
, could you fill a bug as suggested or provide more informations on that package?
Issue 2: listen-on-v6
seems to be missing from your configuration and as the default value changed, this is warning on a behavior change, adding that variable to the configuration with the expected value will solve that part
Issue 3: This is something new, we need to investigate why this is suddenly showing.
Issue 4: It seems that some scripts are relying on /usr/bin/python
. It's preferred to explicitly request python3
or python2
for legacy scripts. I'm curious to know what is using /usr/bin/python
?
thanks
I got past almost this exact same (kernel-uek) error. When i reviewed /var/log/leapp/leapp-upgrade.log it showed dozens of python 3.6 conflicts.
I ran yum remove python3* and remove all python3 packages. reboot. and elevate continued successfully from there.
I got past almost this exact same (kernel-uek) error. When i reviewed /var/log/leapp/leapp-upgrade.log it showed dozens of python 3.6 conflicts.
I ran yum remove python3* and remove all python3 packages. reboot. and elevate continued successfully from there.
The server is not exist anymore, but the python was running by Immunify 360
Sure, I'm guessing that is what the python was on my server for as well. python was reinstalled as a dependent package when immunify was installed again.
@atoomic i've seen this error occur with a couple different users. The common 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)
For me and the two other people (outside of this issue,) #161 being one of them, I resolved this issue by reviewing /var/log/leapp/leapp-upgrade.log
where package conflicts were found. Once the conflicting packages were removed, server rebooted and elevate continued, stage 3, and the rest of the elevation completed successfully.
When the script fails here, there is no mention of /var/log/leapp/leapp-upgrade.log
. Additionally, the other leapp logs do not mention anything about the package conflicts. i stumbled upon the information by just looking through all of the logs leapp generated. I'm wondering if elevate could monitor the leapp-upgrade.log file while in stage 3 for package conflicts and if stage three fails suggest removing said packages as remediation. I reported to http://bugzilla.redhat.com/ as was suggested but as soon as i told them i solved the issue by removing conflicting packages, they closed the ticket, so i don't think they will be taking any action on the issue. I still have all my logs from my failed attempts if they're needed for reference.
@atoomic i've seen this error occur with a couple different users. The common 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)
For me and the two other people (outside of this issue,) #161 being one of them, I resolved this issue by reviewing
/var/log/leapp/leapp-upgrade.log
where package conflicts were found. Once the conflicting packages were removed, server rebooted and elevate continued, stage 3, and the rest of the elevation completed successfully. When the script fails here, there is no mention of/var/log/leapp/leapp-upgrade.log
. Additionally, the other leapp logs do not mention anything about the package conflicts. i stumbled upon the information by just looking through all of the logs leapp generated. I'm wondering if elevate could monitor the leapp-upgrade.log file while in stage 3 for package conflicts and if stage three fails suggest removing said packages as remediation. I reported to http://bugzilla.redhat.com/ as was suggested but as soon as i told them i solved the issue by removing conflicting packages, they closed the ticket, so i don't think they will be taking any action on the issue. I still have all my logs from my failed attempts if they're needed for reference.
welp, This is need to be resolved from their way also, or at least maybe point on the conflicting packages on the CLI.
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)
@danFbach the problem here comes from kernel-uek
which comes from the repository ol8-uek
.
Glad to hear you were able to fix it by removing the package.
We would have to submit a PR to the leapp
project to teach it how to map that package from c7 to c8.
Any chance you can provide me the content of the repo file in /etc/yum.repos.d
where that repoid is listed?
thanks
I would tend to agree with you. I've reopened my ticket and made the suggestion, we'll see if they take any action.
@atoomic Are you just looking for the list of the repos? I can give you the list of what is on my server now, however server is on Alma 8 now though.
-rw-r--r--. 1 root root 943 Nov 19 02:44 almalinux-ha.repo
-rw-r--r--. 1 root root 905 Nov 19 02:44 almalinux-nfv.repo
-rw-r--r--. 1 root root 885 Nov 19 02:44 almalinux-plus.repo
-rw-r--r--. 1 root root 963 Nov 19 02:44 almalinux-powertools.repo
-rw-r--r--. 1 root root 2.7K Nov 19 02:44 almalinux.repo
-rw-r--r--. 1 root root 1.1K Nov 19 02:44 almalinux-resilientstorage.repo
-rw-r--r--. 1 root root 871 Nov 19 02:44 almalinux-rt.repo
-rw-r--r--. 1 root root 928 Nov 19 02:44 almalinux-saphana.repo
-rw-r--r--. 1 root root 873 Nov 19 02:44 almalinux-sap.repo
-rw-r--r--. 1 root root 257 Oct 29 2021 cPAddons.repo
-rw-------. 1 root root 241 Dec 20 00:44 cpanel-plugins.repo
-rw-r--r--. 1 root root 204 Aug 7 2015 EA4.repo
-rw-r--r--. 1 root root 1.7K Oct 3 23:26 epel-modular.repo
-rw-r--r--. 1 root root 1.4K Oct 3 23:26 epel.repo
-rw-r--r--. 1 root root 1.4K Sep 4 2021 epel.repo.rpmnew
-rw-r--r--. 1 root root 1.1K Jun 14 2021 epel.repo.rpmsave
-rw-r--r--. 1 root root 1.8K Oct 3 23:26 epel-testing-modular.repo
-rw-r--r--. 1 root root 1.4K Oct 3 23:26 epel-testing.repo
-rw-r--r--. 1 root root 238 Dec 14 19:13 imunify360.repo
-rw-r--r--. 1 root root 254 Dec 14 19:13 imunify360-testing.repo
-rw-r--r--. 1 root root 2.2K Dec 5 17:25 imunify-rollout.repo
-rw-r--r--. 1 root root 188 Dec 14 19:13 kernelcare.repo
-rw-r--r--. 1 root root 189 Nov 28 13:43 kernelcare.repo.rpmnew
-rw-r--r--. 1 root root 278 Aug 18 00:46 MariaDB102.repo.off
-rw-r--r--. 1 root root 267 Oct 22 2021 MariaDB103.repo.off
-rw-------. 1 root root 158 Dec 14 18:56 MariaDB105.repo
-rw-r--r--. 1 root root 168 Dec 14 18:55 MariaDB105.repo.off
-rw-r--r--. 1 root root 799 Jan 19 2022 Mysql57.repo.off
repoid: ol8-uek does not seem to exist here?
I've reopened my ticket with leapp if you want to hop onto it. 2153539
@danFbach I would like to view the content of the file (not the list) where the repoid ol8-uek
is defined.
something like cat $(grep -l ol8-uek /etc/yum.repos.d/*repo*)
and know which file it is
@atoomic I don't seem to get getting anything, with the command you provided the terminal just hangs.
I also tried grep -GRil 'ol8-uek' /etc/yum.repos.d
which should have produced a similar result, but it came back empty.
Is this repo added and removed during the elevate process?
Thanks for giving it a try. That repo was probably removed at one point.
The elevate
script does not remove repo files.
It can move some repo to *.off
to disable them during the elevate process.
We recommend you open a ticket with cPanel support if you would like further assistance. Thank you!
We been trying the new script, it stuck on stage 3/5.