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.
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.
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.
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