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 1871935 - Need NM OVS DHCP and MTU to work in RHEL 7.9 for OCP [rhel-7.9.z]
Summary: Need NM OVS DHCP and MTU to work in RHEL 7.9 for OCP [rhel-7.9.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks: 1867992 1882667 1884323
TreeView+ depends on / blocked
 
Reported: 2020-08-24 15:56 UTC by Tim Rozet
Modified: 2020-11-10 13:07 UTC (History)
10 users (show)

Fixed In Version: NetworkManager-1.18.8-2.el7_9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-10 13:07:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:5025 0 None None None 2020-11-10 13:07:09 UTC

Description Tim Rozet 2020-08-24 15:56:36 UTC
Description of problem:
OpenShift Container Platform (OCP) uses Network Manager for host networking configuration. In OCP 4.6 (next release) we need the ability for NM to configure an OVS bridge (br-ex) and attach the host physical NIC to the bridge, while also moving the L3 IP addressing (that was previously done on the NIC) to the br-ex ovs interface. This is supported today in RHCOS via fixes that were done for RHEL 8.3/8.2z:

https://bugzilla.redhat.com/show_bug.cgi?id=1852106
https://bugzilla.redhat.com/show_bug.cgi?id=1820052

This works fine for RHCOS today and fixes the previous issues. With OCP, RHCOS is the default operating system used in deployments. However, OCP also supports the option to bring your own RHEL 7.x worker nodes. This means that a customer may choose to use RHEL 7.x as part of an OCP deployment. Therefore those nodes will also be managed by NM and have the same OVS configuration previously mentioned. This BZ is specifically requesting backports for the aforementioned fixes 1852106 and 1820052 into 7.9z.

Comment 2 Thomas Haller 2020-09-04 08:26:55 UTC
Let's do a 7.9-Z-stream update for this, as this affects OCP.

Comment 9 errata-xmlrpc 2020-11-10 13:07:00 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/RHBA-2020:5025


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