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 1878085

Summary: Integrate NetworkManager in dracut (initramfs/initrd) [doc-only, rhel-8.3]
Product: Red Hat Enterprise Linux 8 Reporter: Thomas Haller <thaller>
Component: DocumentationAssignee: Sagar Dubewar <sdubewar>
Documentation sub component: default QA Contact:
Status: CLOSED NOTABUG Docs Contact: Sagar Dubewar <sdubewar>
Severity: medium    
Priority: medium CC: acardace, atragler, bgalvani, cbesson, desktop-qa-list, fgiudici, harald, hartsjc, jmaxwell, lmanasko, lnykryn, lrintel, mmuehlfe, pkotvan, release-test-team-automation, rhel-docs, rkhan, rvykydal, scorreia, sukulkar, thaller, till, vbenes
Version: 8.3Keywords: Reopened
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.2   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
.The `dracut` utility by default now uses NetworkManager in initial RAM disk Previously, the `dracut` utility was using a shell script to manage networking in the initial RAM disk, `initrd`. In certain cases, this could cause problems. For example, the NetworkManager sends another DHCP request, even if the script in the RAM disk has already requested an IP address, which could result in a timeout. With this update, the `dracut` by default now uses the NetworkManager in the initial RAM disk and prevents the system from running into issues. In case you want to switch back to the previous implementation, and recreate the RAM disk images, use the following commands: ---- # echo 'add_dracutmodules+=" network-legacy "' > /etc/dracut.conf.d/enable-network-legacy.conf # dracut -vf --regenerate-all ----
Story Points: ---
Clone Of: 1626348 Environment:
Last Closed: 2020-10-06 14:52:17 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 2020-09-11 09:45:40 UTC
+++ This bug was initially created as a clone of Bug #1577840 +++

Integrate NetworkManager in dracut

* NM is the default in initramfs
* no more dracut network scripts 
* internal test suite passes
* installation with NM in the initrd works



This feature was implemented for rhel-8.2. It was available for users who explicitly opted in to use NetworkManager in initrd/dracut, instead of dracut's network module. This was documented as technology preview in the release-notes for bug 1577840.

In rhel-8.3, RHEL will run NetworkManager in initrd by default. What really changes is only the default. The user still can configure the system to prefer dracuts network module instead.

This is a big change and should be again highlighted for the release notes for rhel-8.3.

The text could be similiar to bug 1577840.

Comment 2 Thomas Haller 2020-09-11 10:12:25 UTC
Oh, of course, I meant this to be a clone of bug 1626348, and not bug 1577840.

Comment 3 Thomas Haller 2020-09-11 10:16:44 UTC
(In reply to Thomas Haller from comment #2)
> Oh, of course, I meant this to be a clone of bug 1626348, and not bug
> 1577840.

both bugs are about the same thing, but one is assigned to dracut and the other to NetworkManager.

Comment 5 Thomas Haller 2020-09-14 11:47:24 UTC
doctext lgtm. Thank you

Comment 8 Thomas Haller 2020-09-15 12:16:04 UTC
I am going to close this bug.

It doesn't seem anything for our QA to test, so adding it to errata seems wrong.
Also, the bug is explicitly about rhel-8.3, so keeping it around longer makes no sense.

The purpose of this rhbz was to track (and discuss) the 8.3 release-note entry for NetworkManager. That is done. If you have anything to add, please reopen (or simply comment).

Comment 10 Thomas Haller 2020-09-15 12:23:04 UTC
ok!

Comment 11 Antonio Cardace 2020-09-24 13:36:02 UTC
Nothing to do for NetworkManager, moving this to documentation.