-
Bug
-
Resolution: Done
-
Major
-
None
-
4.11.z
-
None
Description of problem:
Trying to apply an OVS based scenario fails if the configuration figures the global OVS configuration table - i.e. table name `open` / `open_vswitch` table.
Version-Release number of selected component (if applicable):
Client Version: 4.10.0-0.ci-2021-10-11-040102 Server Version: 4.11.0-0.nightly-2022-09-23-101845 Kubernetes Version: v1.24.0+3882f8f
How reproducible:
Always
Steps to Reproduce:
1. Provision the gist located in https://gist.github.com/maiqueb/b05e8c288ba18bf83eac23314790aee0 . 2. 3.
Actual results:
Failed to configure. This is the error message I see on the NNCE:
```
failed to execute nmstatectl set --no-commit --timeout 480: 'exit status 1'
libnmstate.error.NmstateVerificationError:
desired
=======
---
ovs-db:
external_ids:
ovn-localnet-bridge-mappings: externalvlan:br-underlay
current
=======
---
ovs-db: null
difference
==========
--- desired
+++ current
@@ -1,4 +1,2 @@
---
-ovs-db:
- external_ids:
- ovn-localnet-bridge-mappings: externalvlan:br-underlay
+ovs-db: null
```
Expected results:
The NNCP should apply successfully, and the global OVS configuration table should have the requested attribute.
Additional info:
- clones
-
OCPBUGS-1719 Kubernetes nmstate not able to update global OVS configuration
-
- Closed
-
- is depended on by
-
OCPBUGS-1719 Kubernetes nmstate not able to update global OVS configuration
-
- Closed
-