Bug 1315549

Summary:	openshift-ansible should pre-pull master and client images
Product:	OpenShift Container Platform	Reporter:	Ma xiaoqiang <xiama>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	aos-bugs, bleanhar, jokerman, mmccomas, xtian
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:	2017-08-24 20:48:36 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 Ma xiaoqiang 2016-03-08 02:42:06 UTC

Description of problem:
The steps pre-pulling master and client images were deleted in the following commit:
https://github.com/openshift/openshift-ansible/commit/50b9eefd2b6266b29755e37090138096a2aebc31#diff-433591899fc94e3ef66b3266d8c24eff
But it still pre-pull the node and etcd images


Version-Release number of selected component (if applicable):
openshift-ansible master
commit ID: 0fc6a695eff837ec140e439741fd446a2a10bccf

How reproducible:
100%


Steps to Reproduce:
1. 
2.
3.


Actual results:
openshift-ansible does not pre-pull master and client images


Expected results:
openshift-ansible should pre-pull master and client images

Additional info:

Comment 1 Brenton Leanhardt 2016-03-08 13:21:26 UTC

Is this causing a problem?

I agree we should be consistent whatever we decide.  I suspect the only reason we pre-pull the images is just to keep the systemd startup from timing out.

Comment 2 Ma xiaoqiang 2016-04-18 07:00:42 UTC

It did not cause any issue, just hope the ansible keep consistent in pre-pulling the images. If it will not pre-pull the client and master image, I think it should not pre-pull the node and etcd images.