Closed verdverm closed 6 months ago
pirat89
commented
6 months ago Hi, it's known limitation that's been fixed in version 0.20.0:
The installed version (0.16.0) has been released 2y ago.
verdverm
commented
6 months ago @pirat89 I grabbed the latest master...el7 packages from: https://copr.fedorainfracloud.org/coprs/g/oamg/leapp/packages/
Now I am seeing: Error: Unexpected format of target version: 7 when running leapp preupgrade
Any ideas on what this issue is?
verdverm
commented
6 months ago Seems this is the issue: https://github.com/oamg/leapp-repository/issues/1126
Further complicating the issue is that elevate is not updating the leapp packages, stuck on old versions, so catch 22 for
pirat89
commented
6 months ago yes, that's it.
verdverm
commented
6 months ago For those who come along later, wanting to upgrade Centos7 -> Rocky8 with a local repo mirror
python3 -m http.server 1337 --bind 127.0.0.1 works around the issue, and leapp/dnf see it as a remote repository
We hit an issue where we build a single, minimal yum repo from all the packages we need. This hit another error for a number of packages like...
No available modular metadata for modular package 'fuse-overlayfs-1.12-1.module+el8.9.0+1703+29de406e.x86_64', it cannot be installed on the systemIt seems we have to
createrepo_c instead of createrepo for eachhttps://forums.rockylinux.org/t/fix-no-available-modular-metadata-package-offline-repo/8713
FWIW, we are going to discuss/push for access to the cloud mirrors given how complicated this has become
Actual behavior
Seeing the following error at the last install step before reboot. It only occurs when a repo mirror is created and unpackaged on the machine being upgraded. The context is an airgapped upgrade, so no internet access is possible.
Note, some of these packages are installed earlier from this local mirror
To Reproduce Steps to reproduce the behavior
/etc/leapp/files/leapp_upgrade_repositories.repoto point at the location on vmLEAPP_NOGPGCHECK=1 leapp upgrade --debugExpected behavior
Packages should install as usual.
Note, this process does work if we install from our cloud mirror, rather than the local filesystem. So there is something to narrow down where this might be breaking down.
System information (please complete the following information):
CentOS Linux release 7.9.2009 (Core)# uname -a:3.10.0-1160.59.1.el7.x86_64 #1 SMP Wed Feb 23 16:47:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux# rpm -qa "*leapp*"(or shorthashes of commits in case of manual installation):Attach (or provide link to) log files if applicable (optional - may contain confidential information):
For your convenience you can pack all logs with this command:
# tar -czf leapp-logs.tar.gz /var/log/leapp /var/lib/leapp/leapp.dbThen you may attach only the
leapp-logs.tar.gzfile.Additional context
The repo config file for leapp
Debug logs from the failing command
This line stands out to me, as we tried to disable the gpgcheck everywhere possible
logs...