Bug 1765489

Summary:	Image pull error [Failed to pull image - rpc error: code = Unknown desc = Error: image not found]
Product:	OpenShift Online	Reporter:	kedar <ksalunkh>
Component:	Unknown	Assignee:	Abhishek Gupta <abhgupta>
Status:	NEW ---	QA Contact:	Xiaoli Tian <xtian>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.x	CC:	aos-bugs, yufchang
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 kedar 2019-10-25 09:07:58 UTC

Description of problem:

When setting up a template with a statefulset and an assigned persistent volume,  image pull event occurs. When this error is thrown, the pod won’t never get ready successfully.


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

- openshift v3.11.43


How reproducible:

- cannot be reproduced at all time



Actual results:
The resources like statefulset, serviceaccount, and more are defined within a template. A template has a set of objects. How it can be ensured and configured, that the service account including credentials is created before a statefulset?

Repeated pulling does not solve the problem, although the secret has been created in the meantime. If that case happens (stateful set timestamp < serviceaccount secret) stopping the pod and recreate a new one will solve it.

In the meantime pod can't get the created secret created.



Additional info:
Workaround is killing the pod or deletion of all resources.
the pod can't get the created secret?

Comment 1 kedar 2019-11-04 09:43:54 UTC

Hello,

Any updates on the issue.

Thanks,
Kedar

Comment 2 kedar 2019-11-11 09:24:42 UTC

Hello,

Any updates on the issue.

Thanks,
Kedar

Comment 3 yufchang 2019-11-21 05:46:26 UTC

Hi, Kedar
Could you please attache your template? what is your console address? We will try to reproduce.

Comment 4 kedar 2019-11-25 11:31:19 UTC

Hello,

The issue is been regarding the cu cluster as he stated 

the template alone is not useable without the respective image.
It should be simple for you and your team to reproduce the issue by doing the following steps:

Create a template containing:
- a secret to be created
- an imagestream with an image to be created, referencing the newly created secret as image-puller:
     imagePullSecrets:
     - name: <SECRET_NAME>


Thank you