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.

Description of problem:

(Actually found on CentOS 7, but I have no idea if that is the right place to report it or not)

/etc/init.d/network loops over all interfaces on line 86, on line 87 it unsets some environment variables:

unset DEVICE TYPE SLAVE

However the following environment variables are set:

                eval $(LANG=C grep -F "DEVICE=" ifcfg-$i)
                eval $(LANG=C grep -F "TYPE=" ifcfg-$i)
                eval $(LANG=C grep -F "SLAVE=" ifcfg-$i)
                eval $(LANG=C grep -F "NM_CONTROLLED=" ifcfg-$i)

If you have an eth0 that sets NM_CONTROLLED to "no", and an eth1 that doesn't set NM_CONTROLLED at all, then NM_CONTROLLED will still be set to "no".

This means that all interfaces after the first one (ordered lexically) are going to not be controlled by NetworkManager...

I was dealing with some other issues, so I may or may not have actually hit a bug because of this, but figured I'd report it anyway.

Recommendation:

add NM_CONTROLLED to be unset as well.

Thanks for report. Fixed in upstream https://git.fedorahosted.org/cgit/initscripts.git/commit/

We will include it in some future version of initscripts for rhel/centos7

Of course as a workaround you can explicitly set NM_CONTROLLED=yes for the other devices.

Argh, here is the correct link to upstream
https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=db3e951ab5333a003cfd8276437fb00a71fae334

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, 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-2017:2286