Bug 1276323
Summary: | Most Pod created from guestbook example keep in ImagePullBackOff status although images have been pulled beforehand | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
Component: | Containers | Assignee: | Paul Weil <pweil> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Chao Yang <chaoyang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-23 14:24:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Wenjing Zheng
2015-10-29 13:07:49 UTC
It looks like the images it is trying to pull are both gcr.io images. On my test they took longer than three minutes. Can you verify that gcr.io/google_samples/gb-frontend:v3 is actually on the node in 'docker images'? Thanks, Paul! I just pulled redis, didn't pull gcr.io/google_samples/gb-frontend:v3, pod is running now after images are ready. This fix is available in OpenShift Enterprise 3.1. |