-
Bug
-
Resolution: Can't Do
-
Normal
-
None
-
rhel-9.2.0.z
-
None
-
Moderate
-
rhel-sst-network-management
-
ssg_networking
-
None
-
False
-
-
None
-
None
-
-
None
-
None
-
-
x86_64
-
-
None
What were you trying to do that didn't work?
Applying NNCP policy in OCP cluster resulted in an error. The request is to check the problem with nmstate component.
From the support case:
Have a system with two NICS on the baremetal host. The first NIC is used for Openshift Installation. The Second NIC we wanted to use it as Secondary Network for the Cluster and subsequently use it for VM network. Have initially created an NNCP to configure the second NIC in VLAN mode. Then applied another NNCP to create an OVS bridge on top of it. Based all of these following the procedure documeted here : https://docs.openshift.com/container-platform/4.14/virt/vm_networking/virt-connecting-vm-to-ovn-secondary-network.html The first NNCP is successfully configuring the second NIC in VLAN mode . The second NNCP for the OVN bridge is removing the NIC configuration and is also failing.
Please provide the package NVR for which bug is seen:
OCP 4.14
How reproducible:
Steps to reproduce
- Apply NNCP policy (see attached nncp.yaml).
Expected results
no error.
Actual results
error: "device eno2 could not be added to a ovs port: Error running the transaction: constraint violation: Transaction causes multiple rows in "Bridge" table to have identical values (ovs-br-sec) for index on column "name". First row, with UUID 1871eb7e-4a51-4a1b-8150-c297474e2a4f, existed in the database before this transaction and was not modified by the transaction. Second row, with UUID cf1408e4-49c7-424a-9a0c-68e7f4a0d434, was inserted by this transaction"