Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-52403

Gitops ZTP deployment and it failed and stuck in Inspection during agentcluster install

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Moderate
    • Yes
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Gitops ZTP deployment and it failed and stuck in Inspection with Inspection error during agentcluster install

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

      4.18.2

      How reproducible:

      During spoke cluster installation    

      Steps to Reproduce:

          1.Ran IBU( image based upgrade) pipeline
          2.it got stuck in agent cluster install with inspection error
          3.
          

      Actual results:

      It fails and stuck in inspection error during spoke cluster installation

      Expected results:

      It will install spoke cluster   

      Additional info:---- Logs which i analysed on registry:-

      fatal: [registry.ztp-hub-01.mobius.lab.eng.rdu2.redhat.com]: FAILED! => {"attempts": 80, "changed": true, "cmd": "oc -n kni-qe-2 wait --for=condition=RequirementsMet agentclusterinstall kni-qe-2\n", "delta": "0:00:30.114206", "end": "2025-03-03 08:12:46.805861", "msg": "non-zero return code", "rc": 1, "start": "2025-03-03 08:12:16.691655", "stderr": "error: timed out waiting for the condition on agentclusterinstalls/kni-qe-2", "stderr_lines": ["error: timed out waiting for the condition on agentclusterinstalls/kni-qe-2"], "stdout": "", "stdout_lines": []} 
      Connection to sno.kni-qe-2.lab.eng.rdu2.redhat.com closed. [kni@registry.ztp-hub-01 ~]$ oc get bmh -A NAMESPACE NAME STATE CONSUMER ONLINE ERROR AGE kni-qe-2 sno.kni-qe-2.lab.eng.rdu2.redhat.com inspecting true inspection error 11h
      
      Logs which i analysed on registry:- 
      Mar 03 20:17:30 localhost.localdomain podman[16169]: Error: initializing source docker://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5f24e0d91535caa2f42d20e3c25685737525407fe8e9fb080e2ec73a7ba4d75c: (Mirrors also failed: [registry.ztp-hub-01.mobius.lab.eng.rdu2.redhat.com:5000/openshift-release-dev/ocp-release@sha256:5f24e0d91535caa2f42d20e3c25685737525407fe8e9fb080e2ec73a7ba4d75c: reading manifest sha256:5f24e0d91535caa2f42d20e3c25685737525407fe8e9fb080e2ec73a7ba4d75c in registry.ztp-hub-01.mobius.lab.eng.rdu2.redhat.com:5000/openshift-release-dev/ocp-release: manifest unknown]): quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:5f24e0d91535caa2f42d20e3c25685737525407fe8e9fb080e2ec73a7ba4d75c: pinging container registry quay.io: Get "http://quay.io/v2/": dial tcp [2600:1f18:483:cf02:a1ab:dcce:1a69:9f1e]:80: connect: network is unreachable

              eterrell@redhat.com Eduardo Otubo
              vkhokhar varun khokhar
              varun khokhar
              None
              varun khokhar varun khokhar
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: