Bug 1759430 - Overcloud nodes bootup with non-consistent nic names which are dissimilar to introspection data names, which are consistent
Summary: Overcloud nodes bootup with non-consistent nic names which are dissimilar to ...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-image-elements
Version: 15.0 (Stein)
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: James Slagle
QA Contact: nlevinki
: 1769103 1783104 (view as bug list)
Depends On:
Blocks: 1764508 1884312
TreeView+ depends on / blocked
Reported: 2019-10-08 07:10 UTC by Jaison Raju
Modified: 2023-03-24 15:37 UTC (History)
12 users (show)

Fixed In Version: openstack-tripleo-image-elements-10.4.2-0.20190912000426.1ebd7af.el8ost
Doc Type: Bug Fix
Doc Text:
Previously, the default NIC naming changed to use non-persistent node names such as `ethXX` instead of consistent names like `enoX`, `ensXfY`, `ensX`. As a result, the NIC names present in the introspection data did not match the overcloud NIC names. With this update, the setting `net.ifnames=0` has been removed from grub-config in the overcloud image and the introspection data contains consistent NIC names.
Clone Of:
: 1764508 1884312 (view as bug list)
Last Closed: 2020-03-05 12:00:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
OpenStack gerrit 679169 0 'None' MERGED Clear net.ifnames definition 2020-10-13 19:48:52 UTC
Red Hat Product Errata RHBA-2020:0643 0 None None None 2020-03-05 12:00:57 UTC

Description Jaison Raju 2019-10-08 07:10:48 UTC
Description of problem:
Overcloud nodes, once deployed comes up with ethX name for all types of intel interfaces. These are usually referred to as 'non-persistent nic names' : https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-disabling_consistent_network_device_naming

Although introspection data gives consistent nic names like enoX , ensXfY , ensX etc.
The older versions of RHOS had consistent names in the overcloud.

This difference is due to the 'net.ifnames=0' in grub config.
[root@overcloud-computeovsdpdksriov-1 ~]# grep GRUB_CMDLINE_LINUX /etc/sysconfig/grub
GRUB_CMDLINE_LINUX="console=ttyS0 console=ttyS0,115200n81 no_timer_check net.ifnames=0 crashkernel=auto rhgb quiet"
[root@overcloud-computeovsdpdksriov-1 ~]# cat /proc/cmdline 
BOOT_IMAGE=(hd0,msdos2)/boot/vmlinuz-4.18.0-80.11.1.el8_0.x86_64 root=UUID=064cb90a-9365-4963-9e64-9bc6e71842eb ro console=ttyS0 console=ttyS0,115200n81 no_timer_check net.ifnames=0 crashkernel=auto rhgb quiet default_hugepagesz=1GB hugepagesz=1G hugepages=104 iommu=pt intel_iommu=on isolcpus=2-39 skew_tick=1 nohz=on nohz_full=2-39 rcu_nocbs=2-39 tuned.non_isolcpus=00000003 intel_pstate=disable nosoftlockup

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:
All intel nics are named as ethX names, confusing the user as the introspection data gives different names. Using consistent names would end in deployment / os-net-config failure.

Expected results:
NIC Names seen introspection data should be same as the nic names created by kernel while deployment.
The previous behavior of having enoX , ensX is preferred rather than all nic named as ethX.

Additional info:
I prefer this fix to be in the director image by removing 'net.ifnames=0' in grub config.

Comment 5 Bob Fournier 2019-10-08 15:08:15 UTC
Good find Harald.  This fix has been merged to OSP-15 - https://review.opendev.org/#/c/679169.  It will be in the OSP-15z2 release.

Including DF.

Comment 6 Sai Sindhur Malleni 2019-10-22 10:16:25 UTC
Seeing similar issue in OSP 16

Comment 7 Christopher Brown 2019-11-07 11:32:01 UTC
What concerns me about this is that we will have GA images with one type of nic convention then updated ones with another.

Comment 8 Bob Fournier 2019-11-07 20:59:38 UTC
*** Bug 1769103 has been marked as a duplicate of this bug. ***

Comment 10 Bob Fournier 2019-12-18 12:17:17 UTC
*** Bug 1783104 has been marked as a duplicate of this bug. ***

Comment 11 Alex McLeod 2020-02-19 12:44:15 UTC
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to '-'.

Comment 13 errata-xmlrpc 2020-03-05 12:00:15 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.