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.
Description of problem:
Adding static route(s) to an interface cause the interface to get removed from the list of interfaces managed by NetworkManager.
Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-66.el6.i686
How reproducible:
Always
Steps to Reproduce:
1. Configure static IP for eth0.
2. Add static route for eth0.
Ex: ADDRESS0=224.0.0.0
NETMASK0=240.0.0.0
GATEWAY0=0.0.0.0
3. Save settings and exit.
Actual results:
1. NetworkManager no longer displays eth0 in list of interfaces.
2. Also the network service cannot start eth0 because it is still NM_CONTROLLED=yes and has a UUID entry. So if you reboot, the box is not configuring eth0 anymore and offline.
Workaround:
1. Don't use static routes (i.e. remove route-eth0 file).
OR
2. Use network service (edit ifcfg-eth0 and set NM_CONTROLLED=no and comment-out UUID).
Expected results:
1. NetworkManager still manages eth0 and static routes work.
Additional info:
I am using kernel param "biosdevname=0" to preserve the eth0 network interface naming because I have software licenses tied to "eth0" MAC address.
Can you attach the exact ifcfg/route files that you're using? And what does NM log to /var/log/messages when this happens? Presumably it's disappearing because NM can't parse the config now.
I attached my ifcfg-eth0 and route-eth0 files. If you simply drop the route-eth0 file into /etc/sysconfig/network-scripts folder, the interface disappears from NetworkManager.
Also if I remove the file, NetworkManager doesn't reload the interface unless I "touch ifcfg-eth0".
(In reply to Dan Winship from comment #8)
> It is the same bug, and we have a patch for it. I'll update this bug when we
> have a test package available.
Thanks. Look forward to testing it.
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://rhn.redhat.com/errata/RHBA-2015-1257.html
Description of problem: Adding static route(s) to an interface cause the interface to get removed from the list of interfaces managed by NetworkManager. Version-Release number of selected component (if applicable): NetworkManager-0.8.1-66.el6.i686 How reproducible: Always Steps to Reproduce: 1. Configure static IP for eth0. 2. Add static route for eth0. Ex: ADDRESS0=224.0.0.0 NETMASK0=240.0.0.0 GATEWAY0=0.0.0.0 3. Save settings and exit. Actual results: 1. NetworkManager no longer displays eth0 in list of interfaces. 2. Also the network service cannot start eth0 because it is still NM_CONTROLLED=yes and has a UUID entry. So if you reboot, the box is not configuring eth0 anymore and offline. Workaround: 1. Don't use static routes (i.e. remove route-eth0 file). OR 2. Use network service (edit ifcfg-eth0 and set NM_CONTROLLED=no and comment-out UUID). Expected results: 1. NetworkManager still manages eth0 and static routes work. Additional info: I am using kernel param "biosdevname=0" to preserve the eth0 network interface naming because I have software licenses tied to "eth0" MAC address.