-
Bug
-
Resolution: Unresolved
-
Normal
-
4.18
-
None
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.
- blocks
-
OCPBUGS-45517 Create command fails with "image can't be pulled" error
- ON_QA
- is cloned by
-
OCPBUGS-45517 Create command fails with "image can't be pulled" error
- ON_QA
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update