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 2040683 - Configure route-table and reapply take effect immediately
Summary: Configure route-table and reapply take effect immediately
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Matej Berezny
URL:
Whiteboard:
Depends On:
Blocks: 1914772
TreeView+ depends on / blocked
 
Reported: 2022-01-14 13:39 UTC by Fernando F. Mancera
Modified: 2022-05-10 15:33 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 14:55:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-108188 0 None None None 2022-01-14 13:42:33 UTC
Red Hat Product Errata RHEA-2022:1985 0 None None None 2022-05-10 14:55:37 UTC
freedesktop.org Gitlab NetworkManager NetworkManager-ci merge_requests 917 0 None merged ipv4: added @ipv4_route-table_reapply test 2022-01-31 10:08:41 UTC

Description Fernando F. Mancera 2022-01-14 13:39:35 UTC
Description of problem:

When configuring a profile to use dhcp and route-table, if the user reapply the device, the route-table property won't take effect immediately.

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

1.32.10-4.el8

How reproducible:

100%

Steps to Reproduce:
1. Create a profile with ipv4.method auto and ipv4.route-table 1000
2. Activate the profile
3. Wait until the interface has an IP from DHCP.
4."ip route ls table 1000" should show the routes
5. modify the profile and set ipv4.route-table 1001
6. reapply the device that is using that profile
7. "ip route ls table 1000" should not show any route and "ip route ls table 1001" should show the routes. That is not happening.

Actual results:

The routes are kept on table 1000 instead of 1001 after the reapply.

Expected results:

The routes are on route table 1001 after the reapply.

Comment 5 errata-xmlrpc 2022-05-10 14:55:01 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 (NetworkManager bug fix and enhancement update), 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/RHEA-2022:1985


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