Bug 822989 - /etc/sysconfig/network-scripts/route-* files should be configurable via netcf
Summary: /etc/sysconfig/network-scripts/route-* files should be configurable via netcf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: netcf
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Laine Stump
QA Contact: yalzhang@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-18 17:34 UTC by Laine Stump
Modified: 2020-11-02 19:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-02 19:31:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Laine Stump 2012-05-18 17:34:34 UTC
netcf only reads/writes the ifcfg-* files in /etc/sysconfig/network-scripts, and knows nothing about the interface-specific routes in the route-* files. This is problematic, for example, when a script (or libvirt's virsh) attempts to move an existing interface onto a host bridge - everything about the physical device's configuration is moved over to the bridge, except for the route information which still (incorrectly) points to the physical device.

netcf's XML should be enhanced to allow specifying multiple routes/gateways for each interface. This new XML will then need to be reflected in libvirt's parsing/formatting information for host interfaces.

Comment 1 RHEL Program Management 2012-09-07 05:10:59 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 3 Laine Stump 2015-07-23 15:42:01 UTC
There was insufficient time/resources to implement this feature in time for 7.2, moving to 7.3

Comment 9 Laine Stump 2020-11-02 19:31:19 UTC
There is no demand for this, and it is very unlikely to ever be implemented


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