-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
rhel-9.6
-
No
-
Important
-
1
-
rhel-sst-upgrades
-
None
-
False
-
-
None
-
Leapp: 9.7 & 10.1
-
None
-
None
-
None
What were you trying to do that didn't work?
When the system have nic that named with eth- prefix, the machine still could upgrade via Leapp, but before RHEL9.6, Leapp will prevent upgrading
What is the impact of this issue to you?
Leapp in-place upgrading
Please provide the package NVR for which the bug is seen:
RHEL-9.6.0-20241209.0
kernel-5.14.0-539.el9
How reproducible is this bug?:
Always
Steps to reproduce
- install rhel9.6, there are eth0 nic, want to upgrade to RHEL10, the system could upgrade
kernel-5.14.0-539.el9 6: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 00:15:17:dc:98:dd brd ff:ff:ff:ff:ff:ff 7: ens4f1: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 00:15:17:dc:98:dc brd ff:ff:ff:ff:ff:ff altname enp177s0f1 8: ens4f0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 00:15:17:dc:98:df brd ff:ff:ff:ff:ff:ff altname enp178s0f0 9: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 00:15:17:dc:98:de brd ff:ff:ff:ff:ff:ff rpm -qa | grep leapp leapp-upgrade-el9toel10-deps-0.21.0-4.el9.noarch leapp-deps-0.18.0-4.el9.noarch python3-leapp-0.18.0-4.el9.noarch leapp-0.18.0-4.el9.noarch leapp-upgrade-el9toel10-0.21.0-4.el9.noarch leapp upgrade --debug --no-rhsm --enablerepo AppStream10 --enablerepo BaseOS10 --enablerepo beaker-harness