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

The "default" ingress controller reports Degraded

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.17.0, 4.16.z
    • None
    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

         This is a fllow-up ticket for OCPBUGS-36836, which was closed and was requested to open a ticket per operator. This is one of the tickets for these operators. Now I'm testing ACM 2.12 with OCP 4.17.0-rc1 and latest 4.16.z. and the issues still exist as shown below. please note that I've also tried installing OCP 4.15.29 with ACM 2.12, all 3672 SNO clusters are installed without any issue. 
      the AI logs are uploaded to google drive. Redhatters have view permission: https://drive.google.com/drive/u/1/folders/1m9F7m_YrALUw_XC6su7H19MYRZHM3SBJ?ths=true Feel free to ping me if you need check on the cluster. 
      This ticket is for ingress operator.  
      # oc --kubeconfig=/root/hv-vm/kc/vm00242/kubeconfig get clusteroperators
      NAME                                       VERSION       AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
      authentication                             4.17.0-rc.1   False       False         True       12h     OAuthServerServiceEndpointAccessibleControllerAvailable: Get "https://[fd02::d265]:443/healthz": dial tcp [fd02::d265]:443: connect: connection refused...
      config-operator                            4.17.0-rc.1   True        False         False      12h     
      dns                                        4.17.0-rc.1   True        False         False      12h     
      etcd                                       4.17.0-rc.1   True        False         False      12h     
      ingress                                    4.17.0-rc.1   True        True          True       12h     The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: DeploymentReplicasAllAvailable=False (DeploymentReplicasNotAvailable: 0/1 of replicas are available), CanaryChecksSucceeding=Unknown (CanaryRouteNotAdmitted: Canary route is not admitted by the default ingress controller)
      kube-apiserver                             4.17.0-rc.1   True        False         False      12h     
      kube-controller-manager                    4.17.0-rc.1   True        False         True       12h     GarbageCollectorDegraded: error fetching rules: Get "https://thanos-querier.openshift-monitoring.svc:9091/api/v1/rules": dial tcp: lookup thanos-querier.openshift-monitoring.svc on [fd02::a]:53: server misbehaving
      kube-scheduler                             4.17.0-rc.1   True        False         False      12h     
      kube-storage-version-migrator              4.17.0-rc.1   True        False         False      12h     
      machine-approver                           4.17.0-rc.1   True        False         False      12h     
      machine-config                             4.17.0-rc.1   True        False         False      12h     
      monitoring                                               False       True          True       12h     UpdatingPrometheusOperator: reconciling Prometheus Operator Deployment failed: updating Deployment object failed: waiting for DeploymentRollout of openshift-monitoring/prometheus-operator: context deadline exceeded: got 1 unavailable replicas
      network                                    4.17.0-rc.1   True        False         False      12h     
      node-tuning                                4.17.0-rc.1   True        False         False      12h     
      openshift-apiserver                        4.17.0-rc.1   True        False         False      12h     
      openshift-controller-manager               4.17.0-rc.1   True        False         False      12h     
      operator-lifecycle-manager                 4.17.0-rc.1   True        False         False      12h     
      operator-lifecycle-manager-catalog         4.17.0-rc.1   True        False         False      12h     
      operator-lifecycle-manager-packageserver   4.17.0-rc.1   True        False         False      12h     
      service-ca                                 4.17.0-rc.1   True        False         False      12h          

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              lgamliel liat gamliel
              rhn-support-txue Ting Xue
              Michael Burman Michael Burman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: