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.
Here's another stuck action: http://pastebin.test.redhat.com/941989 (It happened when moving patchA(B) from ovs-brA(B) to ovs-brB(A))
I'm not sure if they have the same root cause, hope it helps.
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-2022:7991
Created attachment 1758445 [details] error log Description of problem: Get stuck when changing ovs-db external-ids. More ovs types were modified, seems it is easier to reproduce. Version-Release number of selected component (if applicable): nmstate-1.0.2-1.el8.noarch nispor-1.0.1-4.el8.x86_64 NetworkManager-1.30.0-0.10.el8.x86_64 openvswitch2.13-2.13.0-79.el8fdp.x86_64 nmstate-plugin-ovsdb-1.0.2-1.el8.noarch How reproducible: Very high Steps to Reproduce: cat << EOF > ovsdb.yaml interfaces: - name: ovs-br0 type: ovs-bridge state: up bridge: port: - name: dummy0 - name: patch0 - name: patch1 - name: veth0 - name: ovsbond0 link-aggregation: mode: balance-slb slaves: - name: veth1 - name: ovs0 - name: dummy0 type: dummy state: up ovs-db: external_ids: this: one - name: ovs0 type: ovs-interface state: up ovs-db: external_ids: this: zero - name: patch0 type: ovs-interface state: up patch: peer: patch1 ovs-db: external_ids: this: two - name: patch1 type: ovs-interface state: up patch: peer: patch0 EOF cat << EOF > full_edit.yaml interfaces: - name: dummy0 ovs-db: external_ids: this: I - name: ovs-br0 ovs-db: external_ids: this: new - name: patch0 ovs-db: external_ids: this: II - name: patch1 ovs-db: external_ids: this: III - name: ovs0 ovs-db: external_ids: this: IV EOF nmstatectl set ovsdb.yaml && nmstatectl set full_edit.yaml Actual results: Failed(stuck) Expected results: No failure Additional info: