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

Create command fails with "image can't be pulled" error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.18
    • oc / node-image
    • None
    • Important
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when you ran the `oc adm node-image create` command, the would sometimes command fail and output an `image can't be pulled` error message. With this release, a fix adds a retry mechanism to the command so that if the command fails to pull images from a release workload, a retry operation ensures the command runs as expected. (link:https://issues.redhat.com/browse/OCPBUGS-45517[*OCPBUGS-45517*])
      Show
      * Previously, when you ran the `oc adm node-image create` command, the would sometimes command fail and output an `image can't be pulled` error message. With this release, a fix adds a retry mechanism to the command so that if the command fails to pull images from a release workload, a retry operation ensures the command runs as expected. (link: https://issues.redhat.com/browse/OCPBUGS-45517 [* OCPBUGS-45517 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-44388. The following is the description of the original issue:
      —
      Description of problem:

          The "oc adm node-image create" command sometimes throw a "image can't be pulled" error the first time the command is executed against a cluster.

Example:

+(./agent/07_agent_add_node.sh:138): case "${AGENT_E2E_TEST_BOOT_MODE}" in
+(./agent/07_agent_add_node.sh:42): oc adm node-image create --dir ocp/ostest/add-node/ --registry-config /opt/dev-scripts/pull_secret.json --loglevel=2
I1108 05:09:07.504614   85927 create.go:406] Starting command in pod node-joiner-4r4hq
I1108 05:09:07.517491   85927 create.go:826] Waiting for pod
**snip**
I1108 05:09:39.512594   85927 create.go:826] Waiting for pod
I1108 05:09:39.512634   85927 create.go:322] Printing pod logs
Error from server (BadRequest): container "node-joiner" in pod "node-joiner-4r4hq" is waiting to start: image can't be pulled

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

          4.18

      How reproducible:

          sometimes

      Steps to Reproduce:

          1. Install a new cluster
    2. Run "oc adm node-image create" to create an image
    3.

      Actual results:

          Error from server (BadRequest): container "node-joiner" in pod "node-joiner-4r4hq" is waiting to start: image can't be pulled

      Expected results:

          No errors

      Additional info:

          The error occurs the first the the command is executed. If one retry running the command again, it succeeds.

              afasano@redhat.com Andrea Fasano
              openshift-crt-jira-prow OpenShift Prow Bot
              Manoj Hans Manoj Hans
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: