Uploaded image for project: 'A-MQ Messaging-as-a-Service'
  1. A-MQ Messaging-as-a-Service
  2. ENTMQMAAS-1867

Console pod stuck CrashLoopBackOff following OCP restart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.4.1
    • 1.4.0, 1.5.0-dev
    • None
    • None

      Following an OCP 4.3 cluster restart the AMQ Online installation was seen to be in the following state:

      console-567b869999-t66c8 1/2 CrashLoopBackOff 44 3h22m
      console-6b964f4c6-47f5n 2/2 Running 2 14h

      The AMQ Online Console operation would have been unaffected, as it would have been served from the other pod.

              keithbwall Keith Wall
              hguerrer Hugo Guerrero (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: