Uploaded image for project: 'Connectivity Link'
  1. Connectivity Link
  2. CONNLINK-376

After restarted OpenShift, Gateway pod is under CrashLoopBackOff state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.0.1
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Gateway pod was terminated with this output: external-istio-7b96bb8555-jq4dp-istio-proxy.log

      2025-03-07T08:16:36.430661Z     error   wasm    convert the wasm config: cannot fetch Wasm module oci://registry.redhat.io/rhcl-1/wasm-shim-rhel9@sha256:458a5ff405922b20142416993f486d22ea23d375f9ef4fc239a42f00649129e4: could not fetch Wasm OCI image: could not fetch manifest: GET https://registry.redhat.io/auth/realms/rhcc/protocol/redhat-docker-v2/auth?scope=repository%3Arhcl-1%2Fwasm-shim-rhel9%3Apull&service=docker-registry: UNAUTHORIZED: Please login to the Red Hat Registry using your Customer Portal credentials. Further instructions can be found here: https://access.redhat.com/articles/3399531; [map[actions:[pull] name:rhcl-1/wasm-shim-rhel9 type:repository]]
      2025-03-07T08:17:05.768417Z     info    Status server has successfully terminated
      2025-03-07T08:17:05.768448Z     info    Agent draining Proxy for termination
      2025-03-07T08:17:05.769478Z     info    Graceful termination period is 5s, starting...
      2025-03-07T08:17:10.772898Z     info    Graceful termination period complete, terminating remaining proxies.
      2025-03-07T08:17:10.772928Z     warn    Aborting proxy
      2025-03-07T08:17:10.772991Z     info    Envoy aborted normally
      2025-03-07T08:17:10.772995Z     warn    Aborted proxy instance
      2025-03-07T08:17:10.773036Z     info    Agent has successfully terminated
      2025-03-07T08:17:10.773375Z     info    ads     ADS: "" 2 terminated
      2025-03-07T08:17:10.773440Z     info    ads     ADS: "" 1 terminated
      

      What I did:

      1. Install OpenShift 4.17 on AWS
      2. Install RHCL follwoing Installing Connectivity Link on OpenShift and Configuring and deploying Gateway policies with Connectivity Link.
      3. Restart the OpenShift follwing Shutting down the cluster gracefully and Restarting the cluster gracefully.
      4. Gateway pod is under CrashLoopBackOff state.
      5. After I deleted and recreated 'external' Gateway resource, the pod became ready state. log: external-istio-7b96bb8555-6wcnm-istio-proxy.log

              tmaas-1 Thomas Maas
              rhn-support-tkonishi Takayuki Konishi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: