Uploaded image for project: 'Konveyor Tackle'
  1. Konveyor Tackle
  2. TACKLE-305

TACKLE on CRC: fails to start after CRC restart, workaround available

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Infrastructure, Operator
    • None
    • False
    • False
    • Undefined
    • None

      Hi all,

      I'm running TACKLE 1.0.0 on CRC (1.27)

      After (re-)starting CRC, Tackle doesn't come up automatically, some Pods are going into a CrashLoopBackOff state.

      Checking some logs, I found that the "tackle-keycloak-*" is the bad boy. It crashes in the init phase. After deleting this Pod, it is being re-spawned and this time works. All other Pods that also have gone into CrashLoopBackOff will recover after keycloak is running (or can safely be deleted to be re-spawned, now working).

       

      [🎩︎mnagel ~]$ crc version
      {{WARN A new version (1.29.1) has been published on https://cloud.redhat.com/openshift/create/local }}
      CodeReady Containers version: 1.27.0+3d6bc39d
      OpenShift version: 4.7.11 (embedded in executable)

       

        1. all_working_now.png
          139 kB
          Markus Nagel
        2. delete_keycloak_pod.png
          19 kB
          Markus Nagel
        3. keycloak_pod_init_prob.png
          141 kB
          Markus Nagel

              mrizzi@redhat.com Marco Rizzi
              mnagel@redhat.com Markus Nagel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: