RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1781136 - Fail to set route rules against two route tables
Summary: Fail to set route rules against two route tables
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-09 12:02 UTC by Gris Ge
Modified: 2023-02-12 22:34 UTC (History)
5 users (show)

Fixed In Version: nmstate-0.2.3-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:00:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
add_route_rule.yml (889 bytes, text/plain)
2019-12-09 12:02 UTC, Gris Ge
no flags Details
verified.log (9.97 KB, text/plain)
2020-02-26 02:30 UTC, Mingyu Shi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-285 0 None None None 2023-02-12 22:34:21 UTC
Red Hat Issue Tracker RHELPLAN-30974 0 None None None 2023-02-12 22:32:15 UTC
Red Hat Product Errata RHBA-2020:1696 0 None None None 2020-04-28 16:00:26 UTC

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


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