-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
rhel-9.6, rhel-9.7
-
None
-
No
-
None
-
rhel-upgrades
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Systems running RHEL 9.7 that use 'eth-' prefixed network interfaces are still eligible for in-place upgrade to RHEL 10. However, systems on RHEL 8 are not supported for direct upgrade to RHEL 9 using Leapp
What is the impact of this issue to you?
Inconsistent behavior
Please provide the package NVR for which the bug is seen:
From RHEL-9.7.0-20250613.3 or newer to rhel10.1-latest
How reproducible is this bug?:
Always
Steps to reproduce
- There're eth- prefix nic on the system
DEVICE TYPE STATE CONNECTION eno1 ethernet connecting (getting IP configuration) eno1 lo loopback connected (externally) lo eno2 ethernet unmanaged -- eno3 ethernet unmanaged -- eno4 ethernet unmanaged -- ens1f0np0 ethernet unmanaged -- ens1f1np1 ethernet unmanaged -- ens4f0 ethernet unmanaged -- ens4f1 ethernet unmanaged -- eth2 ethernet unmanaged -- eth3 ethernet unmanaged --
- Leapp upgrade success,
:: [ 06:36:50 ] :: [ PASS ] :: Command 'leapp upgrade --debug --no-rhsm --enablerepo AppStream10 --enablerepo BaseOS10 --enablerepo beaker-harness' (Expected 0, got 0) REPORT OVERVIEW ============================================================ HIGH and MEDIUM severity reports: 1. GRUB2 core will be automatically updated during the upgrade 2. Packages not signed by Red Hat found on the system 3. Detected modified files of the in-place upgrade tooling. 4. Skipped OS release check 5. Upgrade is unsupported 6. Berkeley DB (libdb) has been detected on your system 7. System-wide crypto policy is set to non-DEFAULT policy Reports summary: Errors: 0 Inhibitors: 0 HIGH severity reports: 5 MEDIUM severity reports: 2 LOW severity reports: 2 INFO severity reports: 2
Expected results
Actual results
- impacts account
-
-
- Planning
-
