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 1883958 - initrd: can't disable NICs during boot
Summary: initrd: can't disable NICs during boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Thomas Haller
QA Contact: Filip Pokryvka
Sagar Dubewar
URL:
Whiteboard:
Depends On:
Blocks: 1875967 1894575
TreeView+ depends on / blocked
 
Reported: 2020-09-30 15:17 UTC by Dusty Mabe
Modified: 2021-05-18 13:31 UTC (History)
11 users (show)

Fixed In Version: NetworkManager-1.30.0-0.1.el8
Doc Type: Bug Fix
Doc Text:
.The `ip=IF_NAME:off` flag now disables both `IPv4` and `IPv6` and saves unexpected delays Previously, setting the `ip=IF_NAME:off` flag in the kernel only disabled `IPv4` on the network interface. Consequently, the NetworkManager was trying to fetch the `IPv6` details and was causing unexpected delays if `IPv6` details were not found. With this update, the `ip=IF_NAME:off` flag now disables both `IPv4` and `IPv6`. As a result, it avoids unexpected delays. However, users from 'ip=IP4::GW::IFACE:none' and relied on having `IPv6` connectivity can use 'ip=IP4::GW::IFACE:link6' or 'ip=IP4::GW::IFACE:auto6' to enable IPv6 connectivity again.
Clone Of:
Environment:
Last Closed: 2021-05-18 13:29:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 665 0 None None None 2020-11-09 15:14:31 UTC

Description Dusty Mabe 2020-09-30 15:17:13 UTC 
Description of problem:

This is a downstream bug with corresponding upstream bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/539

If I have two NICs and I want one to come up and the other one to not attempt any network bringup in the past I specified something like:

- rd.neednet=1
- ip=192.168.122.111::192.168.122.1:255.255.255.0:initrdhost:ens2:none:192.168.122.1
- ip=ens3:off

However this doesn't work as expected now. The system has to timeout the ens3 connection in the initramfs before it comes up.

```
[   36.018249] NetworkManager[724]: <info>  [1601478650.9087] device (ens3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
[   36.021156] NetworkManager[724]: <warn>  [1601478650.9090] device (ens3): Activation: failed for connection 'ens3'
[   36.022372] NetworkManager[724]: <info>  [1601478650.9090] device (ens3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
[   36.023859] NetworkManager[724]: <info>  [1601478650.9111] policy: auto-activating connection 'ens3' (293aad14-25de-4640-ab49-df1f619c3bf6)
[   36.025218] NetworkManager[724]: <info>  [1601478650.9114] device (ens3): Activation: starting connection 'ens3' (293aad14-25de-4640-ab49-df1f619c3bf6)
[   36.026773] NetworkManager[724]: <info>  [1601478650.9115] device (ens3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
[   36.028378] NetworkManager[724]: <info>  [1601478650.9115] device (ens3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
[   36.029772] NetworkManager[724]: <info>  [1601478650.9121] device (ens3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
[   67.003467] NetworkManager[724]: <info>  [1601478681.8947] device (ens3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
[   67.006982] NetworkManager[724]: <warn>  [1601478681.8952] device (ens3): Activation: failed for connection 'ens3'
[   67.008357] NetworkManager[724]: <info>  [1601478681.8952] device (ens3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
[   67.010081] NetworkManager[724]: <info>  [1601478681.8986] policy: auto-activating connection 'ens3' (293aad14-25de-4640-ab49-df1f619c3bf6)
[   67.011288] NetworkManager[724]: <info>  [1601478681.8988] device (ens3): Activation: starting connection 'ens3' (293aad14-25de-4640-ab49-df1f619c3bf6)
[   67.012705] NetworkManager[724]: <info>  [1601478681.8988] device (ens3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
[   67.014057] NetworkManager[724]: <info>  [1601478681.8989] device (ens3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
[   67.015681] NetworkManager[724]: <info>  [1601478681.8995] device (ens3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
[   99.023314] NetworkManager[724]: <info>  [1601478713.9145] device (ens3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
[   99.026982] NetworkManager[724]: <warn>  [1601478713.9149] device (ens3): Activation: failed for connection 'ens3'
[   99.029880] NetworkManager[724]: <info>  [1601478713.9149] device (ens3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
[   99.032386] NetworkManager[724]: <info>  [1601478713.9182] policy: auto-activating connection 'ens3' (293aad14-25de-4640-ab49-df1f619c3bf6)
[   99.033584] NetworkManager[724]: <info>  [1601478713.9184] device (ens3): Activation: starting connection 'ens3' (293aad14-25de-4640-ab49-df1f619c3bf6)
[   99.034871] NetworkManager[724]: <info>  [1601478713.9184] device (ens3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
[   99.036181] NetworkManager[724]: <info>  [1601478713.9184] device (ens3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
[   99.037429] NetworkManager[724]: <info>  [1601478713.9188] device (ens3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
[  131.023105] NetworkManager[724]: <info>  [1601478745.9143] device (ens3): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
[  131.026126] NetworkManager[724]: <warn>  [1601478745.9147] device (ens3): Activation: failed for connection 'ens3'
[  131.027165] NetworkManager[724]: <info>  [1601478745.9147] device (ens3): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
[  131.028510] NetworkManager[724]: <info>  [1601478745.9182] manager: startup complete
[  131.029312] NetworkManager[724]: <info>  [1601478745.9182] quitting now that startup is complete
[  131.030233] NetworkManager[724]: <info>  [1601478745.9187] manager: NetworkManager state is now CONNECTED_SITE
[  131.031227] NetworkManager[724]: <info>  [1601478745.9188] exiting (success)
```


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

NetworkManager-1.26.0-0.2.el8.x86_64



Additional info:

We need this fixed so we don't have a behavior change between RHCOS 4.6 and RHCOS 4.7.
Comment 3 Antonio Cardace 2020-10-09 09:03:49 UTC 
MR in review https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/643.
Comment 4 Beniamino Galvani 2020-10-09 09:54:12 UTC 
The fix for this bug reverts the change that was done for bug 1848943. We agreed that the new behavior makes more sense. I think we should document the change somewhere and perhaps reach out to the reporter of bug 1848943 to explain how to change the command line.
Comment 5 Antonio Cardace 2020-10-09 14:22:09 UTC 
Merged upstream https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/3093a0073b6f578da1a52ee6f44d666e1c254afd.
Comment 15 Thomas Haller 2021-02-02 10:09:24 UTC 
this is a change in behavior and needs to be highlighted in the release notes of 8.4.

See also bug 1909213 which is about this change.
Comment 24 errata-xmlrpc 2021-05-18 13:29:41 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 (Moderate: NetworkManager and libnma security, bug fix, and enhancement update), 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/RHSA-2021:1574
Note You need to log in before you can comment on or make changes to this bug.