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 2012182 - [NMCI] NetworkManager breaks connection to remote rootfs over vlan/bond/bridge created in dracut
Summary: [NMCI] NetworkManager breaks connection to remote rootfs over vlan/bond/bridg...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: NetworkManager
Version: 9.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Wen Liang
QA Contact: Filip Pokryvka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-08 14:23 UTC by Filip Pokryvka
Modified: 2022-05-17 16:07 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.36.0-0.4.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:48:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-99289 0 None None None 2021-10-08 14:28:55 UTC
Red Hat Product Errata RHBA-2022:3915 0 None None None 2022-05-17 15:48:28 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1048 0 None merged core: don't reset assume state if the device is unmanaged by parent 2022-01-13 09:23:58 UTC

Description Filip Pokryvka 2021-10-08 14:23:27 UTC 
Description of problem:
Our dracut testsuite in NetworkManager-ci fails most of the time on RHEL9 (while it is stable on RHEL8), because when NetworkManager is started from root, it cleans the virtual device and atempts to create new. However, with boot over network (NFS, iSCSI), once the connection is down, rootfs is inaccessible and connection never gets restored.

Version-Release number of selected component (if applicable):
1.33.3-29316.copr.098a963e42.fc34

How reproducible:
very often (sometimes some of the tests pass)

Steps to Reproduce:
1. the following tests seems affected:
dracut_NM_vlan_over_bridge
dracut_NM_vlan_over_bond
dracut_NM_bridge_eth0
dracut_NM_bridge_custom_name_2_ifaces
dracut_NM_bond_over_2_ifaces_rr
dracut_NM_vlan_over_nic
dracut_NM_vlan_mutliple_over_nic

Actual results:
tests are unstable

Expected results:
tests should pass consistently, as on rhel8
Comment 1 Wen Liang 2021-12-14 02:30:46 UTC 
After December 6th 2021 (build #731), all the dracut failures listed above were fixed according to the result from the build stats here, https://tools.dqe.lab.eng.bos.redhat.com/vbenes/nm_ci_stats/stats.html#project:beaker-NetworkManager-main-veth-rhel9-upstream;build:;search:dracut.

In order to find out which commit from NM or NM-ci might accidentally fix the dracut test failures, I reproduced the dracut test with different NM version and NM-ci version last Friday, 
 and some random dracut test failures appeared again. I summarized all the test results here, https://docs.google.com/spreadsheets/d/1mXhpOKHmO1u7IzcH4TBWS6T5HZF7Gh_57fRvFjst_eg/edit?usp=sharing.

Based on my investigation, the following dracut test failures appeared again:

```
tests.dracut_NM_vlan_over_nic
tests.dracut_NM_vlan_over_bond
tests.dracut_NM_bridge_eth0
tests.dracut_NM_bond_over_2_ifaces_rr
tests.dracut_NM_vlan_mutliple_over_nic
tests.dracut_NM_vlan_over_bridge
```

In NM log, all the above failures contained the same error (modprobe failed to apply the blacklist command in the configuration files to Linux SCSI Generic driver - `sg` ):

```
Dec 10 13:28:09 localhost.localdomain systemd-udevd[695]: 0:0:0:0: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Dec 10 13:28:09 localhost.localdomain systemd[1]: Starting D-Bus System Message Bus...
Dec 10 13:28:09 localhost.localdomain systemd-udevd[699]: target1:0:0: Process '/sbin/modprobe -bv sg' failed with exit code 1.
Dec 10 13:28:09 localhost.localdomain systemd-udevd[692]: Using default interface naming scheme 'v249'.
Dec 10 13:28:09 localhost.localdomain systemd-udevd[697]: 1:0:0:0: Process '/sbin/modprobe -bv sg' failed with exit code 1.
```
Comment 3 Filip Pokryvka 2022-01-13 15:42:59 UTC 
This seems to be fixed in NetworkManager main branch. Preverifing, when tests pass on the package, I will switch to verified.
Comment 7 Filip Pokryvka 2022-01-20 14:08:20 UTC 
Tests seems stable now on rhel9, verifying.
Comment 10 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
Note You need to log in before you can comment on or make changes to this bug.