Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 85011 - GUI creates route files that boot scripts can't see if interface nicknames used
GUI creates route files that boot scripts can't see if interface nicknames used
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-network (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
Blocks: 81720
  Show dependency treegraph
Reported: 2003-02-24 16:26 EST by Rod Marten
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-11 10:10:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:183 normal SHIPPED_LIVE Updated redhat-config-network package available 2003-08-11 00:00:00 EDT

  None (edit)
Description Rod Marten 2003-02-24 16:26:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
When using the redhat-config-network gui, the files creates route files with the
nickname (vs ethX).  However, ifup-routes relies on the ethX name to find the
interface routes.  As a result interface specific static routes will not be read
on boot.

For example:
My system has eth1 nicknamed InternalInterface.  Interface specific routes are
listed in /etc/sysconfig/networking/devices/InternalInterface.routes. 
ifup-routes looks for eth1.routes and doesn't see InternalInterface.routes.

This is especially troublesome if you create an interface with static routes
then nickname the interface.  Static routes will always be set to the initial
ones no matter how much you try to change them with the GUI due to the fact that
the new route table config isn't loaded

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

How reproducible:

Steps to Reproduce:
1. Create a new ethernet interface
2. Give the interface a nickname
3. Set some static routes on the interface
4. Reboot
5. Check routes with route command

Actual Results:  Interface specific static routes will not appear in the route table

Expected Results:  Interface spedific routes will appear in the route table

Additional info:

Copying the /etc/sysconfig/networking/devices/nickname.route file to
/etc/sysconfig/networking/devices/ethX.route will work as a workaround.
Comment 2 Harald Hoyer 2003-03-31 10:48:31 EST
fixed in CVS
Comment 3 Harald Hoyer 2003-08-11 10:10:19 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.