Bug 1781136

Summary: Fail to set route rules against two route tables
Product: Red Hat Enterprise Linux 8 Reporter: Gris Ge <fge>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.2CC: ferferna, jiji, jishi, network-qe, till
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.2.3-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:00:10 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:
Attachments:
Description Flags
add_route_rule.yml
none
verified.log none

Description Gris Ge 2019-12-09 12:02:21 UTC 
Created attachment 1643279 [details]
add_route_rule.yml

Description of problem:


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

When setting route rules targeting two route tables, nmstate will failed
at the verification stage.

How reproducible:
100%

Steps to Reproduce:
1. Download attached yml file.
2. Execute these commands:
    sudo ip link add eth1 type veth peer name eth1.ep
    sudo ip link add eth2 type veth peer name eth2.ep
    sudo ip link set eth1 up
    sudo ip link set eth1.ep up
    sudo ip link set eth2 up
    sudo ip link set eth2.ep up
    sudo nmcli device set eth1 managed yes
    sudo nmcli device set eth2 managed yes


3. sudo nmstatectl set add_route_rule.yml

Actual results:

nmstate fail at the verification stage.

Expected results:

`ip rule` show the expected route rules.

Additional info:

Upstream patch https://github.com/nmstate/nmstate/pull/637
Comment 1 Gris Ge 2019-12-10 13:03:18 UTC 
Upstream merged my patch.
Comment 6 Mingyu Shi 2020-02-26 02:30:44 UTC 
Created attachment 1665799 [details]
verified.log
Comment 8 errata-xmlrpc 2020-04-28 16:00:10 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:1696