Bug 822989

Summary: /etc/sysconfig/network-scripts/route-* files should be configurable via netcf
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Laine Stump <laine>
Component: netcfAssignee: Laine Stump <laine>
Status: CLOSED WONTFIX QA Contact: yalzhang <yalzhang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ---CC: dyuan, jsuchane, laine, mzhan, xuzhang, yalzhang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-02 19:31:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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