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

[4.14, 4.15] Newly installed IPI cluster on OpenStack starts out with degraded network operator

XMLWordPrintable

    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      After installing OCP 4.14/4.15 on OpenStack using installer, the network operator is stuck in forever updating with the following warnings:
      
      KubeDeploymentReplicasMismatch
      Deployment openshift-cloud-network-config-controller/cloud-network-config-controller has not matched the expected number of replicas for longer than 15 minutes. This indicates that cluster infrastructure is unable to start or restart the necessary components. This most often occurs when one or more nodes are down or partioned from the cluster, or a fault occurs on the node that prevents the workload from starting. In rare cases this may indicate a new version of a cluster component cannot start due to a bug or configuration error. Assess the pods for this deployment to verify they are running on healthy nodes and then contact support.
      
      KubePodCrashLooping
      Pod openshift-cloud-network-config-controller/cloud-network-config-controller-5ffd6646c-wh5pk (controller) is in waiting state (reason: "CrashLoopBackOff").
          

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

      Any 4.14, 4.15
          

      How reproducible:

      Always
          

      Steps to Reproduce:

          1. Install OCP on OpenStack using the installer, we use the following config that worked with OCP 4.13 and before with no issues:
      
      apiVersion: v1
      baseDomain: ${QUARKUS_QE_DOMAIN}
      metadata:
        name: ${OPENSHIFT_CLUSTER_NAME}
      controlPlane:
        name: master
        platform: {}
        replicas: 3
      compute:
      - name: worker
        platform:
          openstack:
            type: ${OPENSTACK_FLAVOR_COMPUTE}
        replicas: 3
      networking:
        clusterNetwork:
        - cidr: 10.128.0.0/14
          hostPrefix: 23
        machineNetwork:
        - cidr: 172.208.0.0/16
        networkType: OVNKubernetes
        serviceNetwork:
        - 172.30.0.0/16
      platform:
        openstack:
          cloud: openstack
          computeFlavor: ${OPENSTACK_FLAVOR_CONTROL_PLANE}
          externalDNS: null
          externalNetwork: ${OPENSTACK_NETWORK}
          lbFloatingIP: ${OPENSTACK_FLOATING_IP_API}
          octaviaSupport: "0"
          region: "regionOne"
          trunkSupport: "1"
      publish: External
      pullSecret: '$(cat ${OPENSHIFT_PULL_SECRET})'
      sshKey: '$(cat ${OPENSHIFT_SSH_KEY})'
          

      Actual results:

      Cluster with unready network operator
          

      Expected results:

      Cluster reporting all operators are ready after install
          

      Additional info:

      
          

            rdobosz Roman Dobosz
            mjurc@redhat.com Michal Jurc
            Itshak Brown Itshak Brown
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: