Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionQuique Llorente
2022-11-11 10:51:15 UTC
Description of problem:
When multiple routes are received over DHCP sometimes is necessary to adjust the metrics to change routes priority
In the case of OVNKubernetes HCO is selecing the wrong primary interface to create the br-ex ovs-bridge on top of it, this means that the default gw with biggest priority will be "br-ex" interface with wrong port.
To fix that the "metric" for the expected primary interface default gw can be increased so traffic goes over there.
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. Change metrics at the DHCP route
routes:
config:
- destination: 0.0.0.0/0
metric: 35
next-hop-address: 10.46.41.254
next-hop-interface: eno1
table-id: 253
Actual results:
Error with "next hop to interface with dynamic IP"
Expected results:
The metrics are changed
Additional info:
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 (nmstate 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/RHBA-2023:2772
Description of problem: When multiple routes are received over DHCP sometimes is necessary to adjust the metrics to change routes priority In the case of OVNKubernetes HCO is selecing the wrong primary interface to create the br-ex ovs-bridge on top of it, this means that the default gw with biggest priority will be "br-ex" interface with wrong port. To fix that the "metric" for the expected primary interface default gw can be increased so traffic goes over there. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Change metrics at the DHCP route routes: config: - destination: 0.0.0.0/0 metric: 35 next-hop-address: 10.46.41.254 next-hop-interface: eno1 table-id: 253 Actual results: Error with "next hop to interface with dynamic IP" Expected results: The metrics are changed Additional info: