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 1904889 - OVS bridge port is deleted when creating a linux-bridge in an Openshift-SDN cluster [rhel-8.3.0.z]
Summary: OVS bridge port is deleted when creating a linux-bridge in an Openshift-SDN c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nmstate
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: rc
: 8.0
Assignee: Fernando F. Mancera
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On: 1903712
Blocks: 1908363
TreeView+ depends on / blocked
 
Reported: 2020-12-07 01:47 UTC by RHEL Program Management Team
Modified: 2020-12-22 09:04 UTC (History)
9 users (show)

Fixed In Version: nmstate-0.3.4-17.el8_3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1903712
Environment:
Last Closed: 2020-12-22 09:04:18 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
verified.log (6.21 KB, text/plain)
2020-12-09 11:01 UTC, Mingyu Shi 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:5659 0 None None None 2020-12-22 09:04:22 UTC

Comment 4 Mingyu Shi 2020-12-07 07:17:39 UTC 
Verified with version: nmstate-0.3.4-16.el8_3.noarch

If only consider this bug itself, with a sanity verification, the fixed version works well, but a situation should be considered: once nmstate rollbacks(for example, you may configure something wrong, or in command line you do 'nmstatectl edit' then just quit without modifying), the vxlan_sys_4789 would be removed.
Comment 5 Petr Horáček 2020-12-07 08:05:45 UTC 
That would be a problem for kubernetes-nmstate. We perform/experience rollbacks quite frequently. We will need that fixed too, otherwise we are just delaying the incident.
Comment 9 Mingyu Shi 2020-12-07 08:16:13 UTC 
trigger(In reply to Mingyu Shi from comment #4)
> Verified with version: nmstate-0.3.4-16.el8_3.noarch
> 
> If only consider this bug itself, with a sanity verification, the fixed
> version works well, but a situation should be considered: once nmstate
> rollbacks(for example, you may configure something wrong, or in command line
> you do 'nmstatectl edit' then just quit without modifying), the
> vxlan_sys_4789 would be removed.

update:
Only if 'vlan_sys_4789' is included in the desired state, then nmstate rollback will remove it, otherwise it is preserved on rollback. The situation is better than I wrote above.
Comment 10 Mingyu Shi 2020-12-07 08:23:06 UTC 
(In reply to Petr Horáček from comment #5)
> That would be a problem for kubernetes-nmstate. We perform/experience
> rollbacks quite frequently. We will need that fixed too, otherwise we are
> just delaying the incident.

Sorry, what I said was partially wrong, can you take a look on #comment9 ? I think it's much better.
Comment 11 Petr Horáček 2020-12-07 08:32:42 UTC 
I see, thanks for the clarification, Mingyu :) Indeed, this looks much better and would not be a problem for kubernetes-nmstate use-case.
Comment 18 Mingyu Shi 2020-12-09 11:01:21 UTC 
Created attachment 1737874 [details]
verified.log

Verified with versions:
NetworkManager-1.26.0-9.el8_3.x86_64
nmstate-0.3.4-17.el8_3.noarch
nmstate-plugin-ovsdb-0.3.4-17.el8_3.noarch
python3-libnmstate-0.3.4-17.el8_3.noarch
DISTRO=RHEL-8.3.0-updates-20201031.0
Linux hpe-dl380pgen8-02-vm-14.hpe2.lab.eng.bos.redhat.com 4.18.0-240.1.1.el8_3.x86_64 #1 SMP Fri Oct 16 13:36:46 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
python3-openvswitch2.13-2.13.0-39.el8fdp.x86_64
openvswitch2.13-2.13.0-39.el8fdp.x86_64
openvswitch-selinux-extra-policy-1.0-22.el8fdp.noarch

If vxlan_sys_4789 is not touched in nmstate, it will always there.
Comment 25 errata-xmlrpc 2020-12-22 09:04:18 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 (Bug fixes for nmstate when using with OpenvSwitch), 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:5659
Note You need to log in before you can comment on or make changes to this bug.