Bug 1718108

Summary: os-net-config ignores routes for SR-IOV PF interfaces
Product: Red Hat OpenStack Reporter: Dan Sneddon <dsneddon>
Component: os-net-configAssignee: Dan Sneddon <dsneddon>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 15.0 (Stein)CC: amcleod, bfournie, hbrock, jslagle, mburns
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: os-net-config-10.4.2-0.20191122070520.ab7364a.el8ost Doc Type: Bug Fix
Doc Text:
Previously, routes on SR-IOV PF interfaces were not set properly and these routes were ignored. With this update, routes for SR-IOV PF interfaces function correctly.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-05 11:59:04 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 Dan Sneddon 2019-06-06 22:54:42 UTC 
Description of problem:
The os-net-config schema has an element for routes for SR-IOV PFs, but they aren't implemented properly. Routes are ignored on SR-IOV PFs.

Version-Release number of selected component (if applicable):
OSP 13 through current versions.

How reproducible:
100%

Steps to Reproduce:
1. Create an SR-IOV PF with routes in the network config template
2. Deploy

Actual results:
Routes on SR-IOV PF interfaces are ignored

Expected results:
Routes should be written to /etc/sysconfig/network-scripts/route-<PF_Iface>, but no routes are written.

Additional info:
The code to handle routes for SR-IOV PFs isn't present in impl_ifcfg.py. They should be handled the same way as other interface types.
Comment 8 Bob Fournier 2020-02-20 16:36:01 UTC 
Verified that os-net-config is now adding routes for SR-IOV PF interfaces.
Comment 10 errata-xmlrpc 2020-03-05 11:59:04 UTC 
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-2020:0643