-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
rhel-7.9
-
None
-
Moderate
-
rhel-sst-upgrades
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
Customer installed package via yum/dnf after running `leapp upgrade` but before rebooting system. This leads to cache error messages with "File not found" and ultimately leapp fails to emergency mode.
[ 70.661973] localhost upgrade[635]: 2024-06-04 20:43:05.220551 [ERROR] Actor: dnf_upgrade_transaction [ 70.661973] localhost upgrade[635]: Message: DNF execution failed with non zero exit code. <snip> [ 71.935560] localhost upgrade[635]: Error opening /var/cache/dnf/rhel-8-for-x86_64-baseos-rpms-376be2e46c653146/packages/bzip2-1.0.6-26.el8.x86_64.rpm: No such file or directory [ 71.935560] localhost upgrade[635]: Package "bzip2-1.0.6-26.el8.x86_64" from repository "rhel-8-for-x86_64-baseos-rpms" has incorrect checksum [ 71.935560] localhost upgrade[635]: Error opening /var/cache/dnf/rhel-8-for-x86_64-baseos-rpms-376be2e46c653146/packages/sos-4.7.1-2.el8_10.noarch.rpm: No such file or directory [ 71.935560] localhost upgrade[635]: Package "sos-4.7.1-2.el8_10.noarch" from repository "rhel-8-for-x86_64-baseos-rpms" has incorrect checksum [ 71.935560] localhost upgrade[635]: Error: Some packages have invalid cache, but cannot be downloaded due to "--cacheonly" option
Please provide the package NVR for which bug is seen:
How reproducible:
Every time
Steps to reproduce
- Run leapp upgrade
- Use dnf/yum to install packages e.g. `yum install sos bzip2`
- Reboot system and it fails to emergency prompt
Expected results
A clear inhibitor pointing to this as the possible cause
Actual results
Unclear inhibitor message
leapp-report.txt shows the following inhibitor:
Risk Factor: high (error) Title: DNF execution failed with non zero exit code. Summary: {"hint": "If there was a problem reaching remote content (see stderr output) and proxy is configured in the YUM/DNF configuration file, the proxy configuration is likely causing this error. Make sure the proxy is properly configured in /etc/dnf/dnf.conf. It's also possible the proxy settings in the DNF configuration file are incompatible with the target system. A compatible configuration can be placed in /etc/leapp/files/dnf.conf which, if present, it will be used during some parts of the upgrade instead of original /etc/dnf/dnf.conf. In such case the configuration will also be applied to the target system. Note that /etc/dnf/dnf.conf needs to be still configured correctly for your current system to pass the early phases of the upgrade process.", "STDERR": "Warning: Package marked by Leapp to install not found in repositories metadata: rpcgen python3-pyxattr\nWarning: Package marked by Leapp to upgrade not found in repositories metadata: gpg-pubkey leapp-upgrade-el7toel8 leapp python2-leapp\nError opening /var/cache/dnf/rhel-8-for-x86_64-baseos-rpms-924d334b319c9ad8/packages/bzip2-1.0.6-26.el8.x86_64.rpm: No such file or directory\nPackage \"bzip2-1.0.6-26.el8.x86_64\" from repository \"rhel-8-for-x86_64-baseos-rpms\" has incorrect checksum\nError opening /var/cache/dnf/rhel-8-for-x86_64-baseos-rpms-924d334b319c9ad8/packages/sos-4.7.1-2.el8_10.noarch.rpm: No such file or directory
I think we can improve this message so that it mentions not to perform yum/dnf transactions after running 'leapp upgrade'
- links to