Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-32535

Applying NNCP policy resulted in constraint violation error

    • None
    • Moderate
    • rhel-sst-network-management
    • ssg_networking
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Given a system administrator is configuring an OCP 4.14 cluster with a NodeNetworkConfigurationPolicy to create an OVS bridge (See attached nncp.yaml file), 

      When the NNCP policy is applied to configure the bridge, 

      Then, the configuration should complete successfully without triggering a "constraint violation" error or any other system errors, effectively establishing the bridge.

       

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are written and pass
      • The fix is part of a downstream build attached to an errata
      • The fix is backported into RHEL-9.2.z
      Show
      Given a system administrator is configuring an OCP 4.14 cluster with a NodeNetworkConfigurationPolicy to create an OVS bridge (See attached nncp.yaml file),  When the NNCP policy is applied to configure the bridge,  Then, the configuration should complete successfully without triggering a "constraint violation" error or any other system errors, effectively establishing the bridge.   Definition of Done: The implementation meets the acceptance criteria Integration tests are written and pass The fix is part of a downstream build attached to an errata The fix is backported into RHEL-9.2.z
    • 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

      1. Apply NNCP policy (see attached nncp.yaml).
      2.  
      3.  

      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"

        1. nncp.yaml
          1 kB
        2. nncp_vlan_slabnode2200.yaml
          0.7 kB
        3. nncp_bridge.yaml
          0.6 kB
        4. nncp_bridge(1).yaml
          0.6 kB
        5. nncp_with_typo.yaml
          1 kB

              rh-ee-sfaye Stanislas Faye
              ibodunov Ivan Bodunov
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: