Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-26580

[ROSA HCP]Ingress degraded before deletion or restoration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Fleet Manager
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • OSDFM Sprint 1
    • None

      New cluster ingress certificates stuck in "NOT Ready" state for hours, on Nov 13th

      ingress 4.19.17 True True True 62m The "default" ingress controller reports Degraded=True: DegradedConditions: One or more other status conditions indicate a degraded state: DeploymentReplicasAllAvailable=False (DeploymentReplicasNotAvailable: 1/2 of replicas are available).

      Cluster pods for openshift-ingress

      oc get pods -n openshift-ingress --kubeconfig /Users/emathias/GitLab/ocm-backend-tests/output/.datainfo/kube-configs/2mholilfa3lvc7tt4ntu123orfo0oueo.kubeconfig
      NAME READY STATUS RESTARTS AGE
      router-default-575b475698-ktrrh 0/1 ContainerCreating 0 70m
      router-default-575b475698-x8998 0/1 ContainerCreating 0 70m
      router-default-7794f9db6-9xjr2 1/1 Running 0 66m

      Slack thread: https://redhat-internal.slack.com/archives/C089VJ638AY/p1763031226275959

              rh-ee-chlu Chee Lu
              elveeram Elveera Mathias
              Anna Francis Anna Francis
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: