Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1980387

Summary:	[RFE] NetworkManager ignores rd.znet_ifname kernel command line option on s390x
Product:	Red Hat Enterprise Linux 9	Reporter:	Filip Pokryvka <fpokryvk>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lrintel>
Status:	CLOSED ERRATA	QA Contact:	Filip Pokryvka <fpokryvk>
Severity:	unspecified	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	high
Version:	9.0	CC:	bgalvani, ferferna, fge, gfialova, lrintel, rkhan, sukulkar, thaller, till
Target Milestone:	beta	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.36.0-0.7.el9	Doc Type:	Enhancement
Doc Text:	.NetworkManager supports interface names set in the `rd.znet_ifname` kernel option on IBM Z With this enhancement, on the IBM Z platform, NetworkManager now interprets the `rd.znet` and `rd.znet_ifname` kernel command-line options when installing or booting Red Hat Enterprise Linux from the network. As a result, it is possible to specify a name of a network interface identified by the subchannels instead of the default one.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-17 15:48:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Filip Pokryvka 2021-07-08 14:25:10 UTC

Description of problem:
rd.znet_ifname command line option is currently ignored by NetworkManger initrd generator. According to `man dracut.cmdline`, it renames interface with matching subchannels. NetworkManager should not use predictable name in that case and map rd.znet option accordingly.

Version-Release number of selected component (if applicable):
1.32.0-1.el9

How reproducible:
always

Steps to Reproduce:
/usr/libexec/nm-initrd-generator -s -- rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=1,portname=foo rd.znet_ifname=eth0:0.0.0600,0.0.0601,0.0.0602 ip=eth0:auto

Actual results:
Connection for eth0 is generated, but does not have s390-options and s390-subchannels set.

Expected results:
Connection for eth0 should have s390-options and s390-subchannels set (as if ip=enc600:auto was used instead of eth0).

Additional info:
replacing rd.znet_ifname=eth0:0.0.0600,0.0.0601,0.0.0602 by net.ifnames=0 works (however only if eth0 is desired name, otherwise it does not work).

Comment 1 Gris Ge 2021-07-14 06:07:07 UTC

Hi Beniamino,

Can NetworkManager rename a interface in this use case?

Comment 2 Beniamino Galvani 2021-07-14 07:16:11 UTC

(In reply to Gris Ge from comment #1)
> Can NetworkManager rename a interface in this use case?

Note that here "rename" doesn't mean that NetworkManager changes the link name, because that is already done by the 'znet' dracut module using a udev rule.

What NM should do is to generate a connection using the name from `rd.znet_ifname` instead of building the name according to subchannels and other properties from 'rd.znet'.

This is a missing feature and can be implemented.

Comment 7 Thomas Haller 2022-01-26 21:57:46 UTC

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/68f500f5cee9c784fda4399e0839fc9b705457a4

Comment 8 Thomas Haller 2022-01-26 22:04:31 UTC

the code comes with a unit test, which looks sensible, runs and passes.
I didn't test an actual boot, due to the effort of piecing initrd together.
But the initrd generator appears to work as intended.

Marking pre-verified.

Comment 11 Filip Pokryvka 2022-02-17 10:00:31 UTC

This is covered by unit tests of nm-initrd-generator utility. I have checked manually and works fine now, connection is matched by rd.znet_ifname option.

Comment 18 errata-xmlrpc 2022-05-17 15:48: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 (new packages: NetworkManager), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2022:3915