Bug 1657737

Summary:	Control plane images should always be pulled during upgrades
Product:	OpenShift Container Platform	Reporter:	Pablo Alonso Rodriguez <palonsor>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Installer sub component:	openshift-ansible	QA Contact:	Johnny Liu <jialiu>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	per.carlson
Version:	3.10.0
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:	2018-12-13 14:53:50 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 Pablo Alonso Rodriguez 2018-12-10 10:58:47 UTC

Description of problem:

During upgrade between minor 3.10 versions, ose-control-plane:v3.10 is not pulled again from registries. So, as the image is already available at docker daemons of masters, it is still at the oldest 3.10 version.

Version-Release number of the following components:

(see private comments)

How reproducible:

At the moment, reproduced at the customer. But it should be easy to reproduce with just a single control plane update between minor releases.

Steps to Reproduce:
1. We start with a 3.10 cluster that is not at latest 3.10 version. It is very important, that ose-control-plane:v3.10 are already present on master docker daemons and match the version of the cluster (not the latest one).
2. Upgrade the cluster to the latest version with the playbooks
3. Check the version of ose-control-plane:v3.10 image at masters after upgrade (for example, by examining the sha256 sums)

Actual results:
ose-control-plane:v3.10 at masters are the ones of the old version, instead of the ones of the latest version (as per sha256 sums)

Expected results:
ose-control-plane:v3.10 should be at latest version

Additional info:

Comment 4 Scott Dodson 2018-12-13 14:53:50 UTC


*** This bug has been marked as a duplicate of bug 1658387 ***