RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2094284 - NIC name unexpectedly changes back to PCI-based style after the RHEL9.0 GA
Summary: NIC name unexpectedly changes back to PCI-based style after the RHEL9.0 GA
Keywords:
Status: CLOSED DUPLICATE of bug 2073003
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: systemd
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-07 10:47 UTC by Zhiqian Guan
Modified: 2022-06-08 16:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-08 16:51:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-124455 0 None None None 2022-06-07 11:03:01 UTC

Description Zhiqian Guan 2022-06-07 10:47:53 UTC 
Description of problem:

The network interface name changed back to PCI-based style when using systemd-250-7.el9.x86_64 with RHEL 9.1 kernel. 

The nic name has been migrated to slot-based names in the later 9.0 cycle. And now it's changed back to PCI-based names in the 9.1 cycle, which I believe is unexpected.

Version-Release number of selected component (if applicable):
systemd-250-7.el9.x86_64
5.14.0-105.el9.x86_64

How reproducible:
always

Steps to Reproduce:
1. Provision a system with 9.0 GA distro
2. use ip add to check the network interface
3. Re-provision the system with a 9.1 distro, here I used RHEL-9.1.0-20220605.0
4. use ip add to check the network interface

Actual results:
In the 9.1 distro, the NIC name is PCI based

Expected results:
based on the discussion before, the nic name should be slot-based in RHEL9

Additional info:

============== provision system with RHEL9 GA distro ====================

[root@netqe2 ~]# ip ad
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:48:ed:f4:bd:04 brd ff:ff:ff:ff:ff:ff
    altname enp24s0f0
    inet 10.19.15.7/24 brd 10.19.15.255 scope global dynamic noprefixroute eno1
       valid_lft 83777sec preferred_lft 83777sec
    inet6 2620:52:0:130f:3648:edff:fef4:bd04/64 scope global dynamic noprefixroute
       valid_lft 2591991sec preferred_lft 604791sec
    inet6 fe80::3648:edff:fef4:bd04/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:48:ed:f4:bd:05 brd ff:ff:ff:ff:ff:ff
    altname enp24s0f1
4: ens5f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 40:a6:b7:2f:a9:a0 brd ff:ff:ff:ff:ff:ff
    altname enp134s0f0
5: ens5f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 40:a6:b7:2f:a9:a1 brd ff:ff:ff:ff:ff:ff
    altname enp134s0f1
6: ens3f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 90:e2:ba:c3:cb:b0 brd ff:ff:ff:ff:ff:ff
    altname enp94s0f0
7: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:96:91:a0:3f:7e brd ff:ff:ff:ff:ff:ff
    altname enp59s0f0
8: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:48:ed:f4:bd:06 brd ff:ff:ff:ff:ff:ff
    altname enp25s0f0
9: ens3f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 90:e2:ba:c3:cb:b1 brd ff:ff:ff:ff:ff:ff
    altname enp94s0f1
10: ens4f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 24:8a:07:87:23:f2 brd ff:ff:ff:ff:ff:ff
    altname enp175s0f0np0
11: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:48:ed:f4:bd:07 brd ff:ff:ff:ff:ff:ff
    altname enp25s0f1
12: ens1f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:96:91:a0:3f:7f brd ff:ff:ff:ff:ff:ff
    altname enp59s0f1
13: ens4f1np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 24:8a:07:87:23:f3 brd ff:ff:ff:ff:ff:ff
    altname enp175s0f1np1
[root@netqe2 ~]#
[root@netqe2 ~]#
[root@netqe2 ~]# uname -r
5.14.0-70.14.1.el9_0.x86_64
[root@netqe2 ~]# rpm -q systemd
systemd-250-6.el9_0.x86_64


================ Re-provision the same system with RHEL-9.1.0-20220605.0 =======
[root@netqe2 ~]#
[root@netqe2 ~]# uname -r
5.14.0-105.el9.x86_64
[root@netqe2 ~]# ip ad
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 34:48:ed:f4:bd:04 brd ff:ff:ff:ff:ff:ff
    altname enp24s0f0
    inet 10.19.15.7/24 brd 10.19.15.255 scope global dynamic noprefixroute eno1
       valid_lft 85434sec preferred_lft 85434sec
    inet6 2620:52:0:130f:3648:edff:fef4:bd04/64 scope global dynamic noprefixroute
       valid_lft 2591876sec preferred_lft 604676sec
    inet6 fe80::3648:edff:fef4:bd04/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: enp134s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 40:a6:b7:2f:a9:a0 brd ff:ff:ff:ff:ff:ff
4: enp134s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 40:a6:b7:2f:a9:a1 brd ff:ff:ff:ff:ff:ff
5: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:48:ed:f4:bd:05 brd ff:ff:ff:ff:ff:ff
    altname enp24s0f1
6: enp59s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:96:91:a0:3f:7e brd ff:ff:ff:ff:ff:ff
7: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:48:ed:f4:bd:06 brd ff:ff:ff:ff:ff:ff
    altname enp25s0f0
8: enp94s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 90:e2:ba:c3:cb:b0 brd ff:ff:ff:ff:ff:ff
9: enp175s0f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 24:8a:07:87:23:f2 brd ff:ff:ff:ff:ff:ff
10: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 34:48:ed:f4:bd:07 brd ff:ff:ff:ff:ff:ff
    altname enp25s0f1
11: enp59s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether b4:96:91:a0:3f:7f brd ff:ff:ff:ff:ff:ff
12: enp94s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 90:e2:ba:c3:cb:b1 brd ff:ff:ff:ff:ff:ff
13: enp175s0f1np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 24:8a:07:87:23:f3 brd ff:ff:ff:ff:ff:ff
[root@netqe2 ~]#
[root@netqe2 ~]# rpm -q systemd
systemd-250-7.el9.x86_64
[root@netqe2 ~]# uname -r
5.14.0-105.el9.x86_64
[root@netqe2 ~]#
Comment 1 Michal Sekletar 2022-06-08 16:51:12 UTC 
This is unexpected and it happened because RHEL-9 and CentOS stream got out of sync during the run up to GA date (during blocker+exception phase) when the RHEL workflow is essentially already z-stream workflow. Bugs that got fixed in that time period were cloned against RHEL-9.1 and are already marked as accepted blockers (e.g. https://bugzilla.redhat.com/show_bug.cgi?id=2073003) and will be fixed in one of the following builds.

*** This bug has been marked as a duplicate of bug 2073003 ***
Note You need to log in before you can comment on or make changes to this bug.