Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-38422

NNCP stuck on ConfigurationProgressing state during performance

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.15.0
    • None
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Test creating NNCP connected to the host NIC over performnce lab - total of 6 nodes, one of the NNCP is stuck on ConfigurationProgressing, this is despite all the nodes appeared to be configured successfully.    

      Version-Release number of selected component (if applicable):

      OCP 4.15.31 NMState operator 4.15.0    

      How reproducible:

          

      Steps to Reproduce:

          1. Create a 6 node cluster
          2. Deploy 400 NNCP
          

      Actual results:

      All NNCP in status SuccessfullyConfigured     

      Expected results:

      One NNCP stuck in status ConfigurationProgressing

      Additional info:

      My NNCP json :    
      
      {
        "apiVersion": "nmstate.io/v1",
        "kind": "NodeNetworkConfigurationPolicy",
        "metadata": {
          "name": "br-nncp-scale-{{index}}"
        },
        "spec": {
          "desiredState": {
            "interfaces": [
              {
                "name": "br-scale-{{index}}",
                "type": "linux-bridge",
                "state": "up",
                "bridge": {
                  "options": {
                    "stp": {
                      "enabled": false
                    }
                  }
                },
                "ipv4": {
                  "enabled": false,
                  "dhcp": false
                },
                "ipv6": {
                  "enabled": false
                }
              },
              {
                "name": "{{base_interface}}.{{index}}",
                "type": "vlan",
                "state": "up",
                "vlan": {
      
                  "base-iface": "{{base_interface}}",
                  "id": "{{index}}"
                }
              }
            ]
          },
          "nodeSelector": {
            "node-role.kubernetes.io/worker": ""
          }
        }
      }
      
      All bridge are configured on the nodes :
      oc get nodes -l node-role.kubernetes.io/worker -o name | xargs -I{} sh -c 'echo -n \"{}: \"; oc describe {} | awk "/Allocated resources/,/Events:/ {print}" | grep -c "bridge.network.kubevirt.io/br-scale-"'
      "node/e31-h02-000-r640: "400
      "node/e31-h03-000-r640: "400
      "node/e31-h05-000-r640: "400
      "node/e31-h06-000-r640: "400
      "node/f04-h13-000-r640: "400
      "node/f04-h32-000-r640: "400
      "node/f04-h33-000-r640: "400

              mkowalsk@redhat.com Mat Kowalski
              guchen11 Guy Chen
              Qiong Wang Qiong Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: