-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-8.10
-
No
-
Critical
-
1
-
rhel-sst-upgrades
-
26
-
None
-
False
-
-
None
-
Leapp: 9.8 & 10.2
-
None
-
None
-
None
What were you trying to do that didn't work?
Leapp on azure form RHEL 8 to RHEL 9
Please provide the package NVR for which the bug is seen:
How reproducible is this bug?:
everytime
Steps to reproduce
# dnf config-manager --set-enabled rhui-microsoft-azure-rhel8 # dnf -y install rhui-azure-rhel8 leapp-rhui-azure # yum update # reboot # yum install leapp-upgrade # leapp preupgrade --no-rhsm
Expected results
It should enable baseos and appstream for the upgrade
Actual results
only baseos is being enabled.
Risk Factor: high (error) Title: DNF execution failed with non zero exit code. Summary: {"STDOUT": "Last metadata expiration check: 0:01:33 ago on Fri Sep 6 06:29:43 2024. Package xorg-x11-font-utils-1:7.5-41.el8.x86_64 is already installed. ", "STDERR": "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: Package marked by Leapp to install not found in repositories metadata: perl-FileHandle perl-fields perl-filetest perl-Class-Struct perl-Time perl-less python3-file-magic perl-Thread perl-Net perl-I18N-LangTags perl-FindBin perl-Search-Dict perl-overloading perl-Thread-Semaphore rsyslog-logrotate perl-Safe perl-Tie perl-subs perl-autouse perl-Hash-Util-FieldHash perl-Config-Extensions perl-Tie-RefHash perl-locale perl-NDBM_File perl-File-stat perl-Dumpvalue perl-SelectSaver perl-vmsish perl-encoding-warnings perl-User-pwent perl-Symbol perl-lib perl-meta-notation perl-mro perl-File-Basename perl-vars perl-blib perl-AutoLoader perl-Fcntl perl-Term-ReadLine perl-Sys-Hostname perl-B xfsprogs-xfs_scrub perl-Benchmark perl-File-Copy perl-ExtUtils-Constant perl-File-DosGlob perl-Tie-File perl-File-Find perl-Getopt-Std perl-Hash-Util perl-if perl-debugger perl-FileCache perl-I18N-Collate perl-I18N-Langinfo perl-English perl-deprecate perl-Unicode-UCD perl-Text-Abbrev perl-Opcode perl-doc perl-GDBM_File perl-IPC-Open3 perl-sigtrap perl-NEXT perl-sort jitterentropy-devel perl-base perl-DBM_Filter perl-DirHandle perl-Term-Complete perl-File-Compare perl-Tie-Memoize perl-ODBM_File perl-ph perl-Pod-Functions perl-diagnostics perl-DynaLoader perl-POSIX perl-AutoSplit perl-overload Warning: Package marked by Leapp to upgrade not found in repositories metadata: python3-leapp leapp-upgrade-el8toel9 gpg-pubkey leapp Transaction check: Problem 1: conflicting requests Problem 2: package policycoreutils-python-utils-2.9-26.el8_10.noarch from @System requires python3-policycoreutils = 2.9-26.el8_10, but none of the providers can be installed - package python3-policycoreutils-2.9-26.el8_10.noarch from @System requires python(abi) = 3.6, but none of the providers can be installed - package leapp-repository-deps-el9-5.0.9-100.202401121819Z.0e51aebb.master.el9.noarch from @commandline requires policycoreutils-python-utils, but none of the providers can be installed - conflicting requests Problem 3: package policycoreutils-python-utils-2.9-26.el8_10.noarch from @System requires python3-policycoreutils = 2.9-26.el8_10, but none of the providers can be installed - package leapp-repository-deps-el9-5.0.9-100.202401121819Z.0e51aebb.master.el9.noarch from @commandline requires policycoreutils-python-utils, but none of the providers can be installed - package python3-policycoreutils-2.9-26.el8_10.noarch from @System requires python(abi) = 3.6, but none of the providers can be installed - package leapp-upgrade-el8toel9-0.20.0-2.el8.noarch from @System requires leapp-repository-dependencies = 10, but none of the providers can be installed - platform-python-3.6.8-62.el8_10.x86_64 from @System does not belong to a distupgrade repository - leapp-upgrade-el8toel9-deps-0.20.0-2.el8.noarch from @System does not belong to a distupgrade repository - problem with installed package leapp-upgrade-el8toel9-0.20.0-2.el8.noarch ", "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."} Key: 1e26c8b86cec72c25c04ca045d2b0ed3e8ca2df5