-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
rhel-8.10.z
-
No
-
Low
-
rhel-upgrades
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
Having the valgrind-scripts-1:3.22.0-3.el8_10.x86_64 package installed on a RHEL 8.10 system creates a conflict for the target RHEL 9.4 valgrind-1:3.22.0-2.el9.x86_64 package.
warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend. warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend. warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend. warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend. warning: Found bdb_ro Packages database while attempting sqlite backend: using bdb_ro backend. Error: Transaction test error: file /usr/bin/cg_annotate from install of valgrind-1:3.22.0-2.el9.x86_64 conflicts with file from package valgrind-scripts-1:3.22.0-3.el8_10.x86_64 file /usr/bin/cg_diff from install of valgrind-1:3.22.0-2.el9.x86_64 conflicts with file from package valgrind-scripts-1:3.22.0-3.el8_10.x86_64 file /usr/bin/cg_merge from install of valgrind-1:3.22.0-2.el9.x86_64 conflicts with file from package valgrind-scripts-1:3.22.0-3.el8_10.x86_64 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.
What is the impact of this issue to you?
Breaking the leapp upgrade from RHEL 8.10 to RHEL 9.4 upgrade path.
Steps to reproduce
- Install the valgrind-scripts package on RHEL 8.10
- Try performing a leapp upgrade from RHEL 8.10 to RHEL 9.4
Expected results
Actual results
- duplicates
-
RHEL-84978 Leapp upgrade from RHEL 8.10 to RHEL 9.x fails when Valgrind packages are installed
-
- Closed
-