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 1783996

Summary:	Document NetworkManager in initrd as tech preview for rhel-8.2
Product:	Red Hat Enterprise Linux 8	Reporter:	Thomas Haller <thaller>
Component:	Documentation	Assignee:	Lucie Vařáková <lmanasko>
Documentation sub component:	default	QA Contact:	RHEL DPM <rhel-docs>
Status:	CLOSED CURRENTRELEASE	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Severity:	unspecified
Priority:	medium	CC:	rhel-docs, rvykydal
Version:	8.2	Keywords:	Documentation
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Technology Preview
Doc Text:	See Doc Text field in BZ#1626348.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-01-15 11:35:39 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 Thomas Haller 2019-12-16 12:51:58 UTC

When doing networking from early boot (dracut, initrd), then currently dracut runs the "network-legacy" module. This essentially runs dhclient in initrd. In later boot, NetworkManager is supposed to take over. That has many issues and bugs, because NetworkManager has no proper API where it could be told about the previous networking configuration done in initrd. 

The intended solutions is to also run NetworkManager in initrd, because NetworkManager will know how to hand over the configured network to a later version of itself. The other reason for doing this are that the current network-legacy module is very limited (compared to what is or will be possible with NetworkManager). Also, we avoid implementing multiple mechanisms for configuring networking and an API how one mechanism hands over to the other.

This is basically bug 1626348.

For rhel-8.2, this was not yet ready and got postponed to switch the default to rhel-8.3. However, all the bits are in place already and a user (who has issues with the current dracut module) could already use the new way. So, while this is not yet the default in rhel-8.2, the user can opt-in.

This bug is about documenting this opt-in as Tech Preview for rhel-8.2. This opt-in is tracked by bug 1774438.


(note that for rhel-8.3, the plan is this to become the default!)

Comment 1 Thomas Haller 2019-12-17 10:01:01 UTC

see https://bugzilla.redhat.com/show_bug.cgi?id=1774438#c18 for how to enable it via kickstart/anaconda.

Comment 2 Marc Muehlfeld 2020-01-15 11:35:39 UTC

I attached the RN to the development ticket (BZ#1626348).
The RN contains the steps to enable the feature.