Bug 1904889
| Summary: | OVS bridge port is deleted when creating a linux-bridge in an Openshift-SDN cluster [rhel-8.3.0.z] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> | ||||
| Component: | nmstate | Assignee: | Fernando F. Mancera <ferferna> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Mingyu Shi <mshi> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 8.3 | CC: | ellorent, ferferna, fge, jiji, jishi, myakove, network-qe, phoracek, till | ||||
| Target Milestone: | rc | Keywords: | Triaged, ZStream | ||||
| Target Release: | 8.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | nmstate-0.3.4-17.el8_3 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1903712 | Environment: | |||||
| Last Closed: | 2020-12-22 09:04:18 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1903712 | ||||||
| Bug Blocks: | 1908363 | ||||||
| Attachments: |
|
||||||
|
Comment 4
Mingyu Shi
2020-12-07 07:17:39 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. 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. (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. I see, thanks for the clarification, Mingyu :) Indeed, this looks much better and would not be a problem for kubernetes-nmstate use-case. 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.
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 |