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

console-mce pod CrashLoopBackOff due to probe failure

XMLWordPrintable

    • 0
    • False
    • Hide

      None

      Show
      None
    • False
    • ACM Console Train 32 - 2
    • None

      Description of problem:

      console-mce pods are in CrashLoopBackOff due to readiness and liveness probe failure.  

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

      2.13

      Additional info:

      We increased the timeout seconds for console-mce-console deployment to 10 seconds and that resolved their issue but after 1 or 2 days, changes got reverted back and timeoutSeconds were changed back to 5 seconds 

      containers:
      - env:
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /livenessProbe
            port: 3000
            scheme: HTTPS
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 5.  <--
        name: console
        ports:
        - containerPort: 3000
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /readinessProbe
            port: 3000
            scheme: HTTPS
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 5. <---

              rh-ee-kcormier Kevin Cormier
              rhn-support-shrsharm Shreya Sharma
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: