Bug 1563247

Summary:	jenkins-slave-maven-rhel7 latest used on older version
Product:	OpenShift Container Platform	Reporter:	Vladislav Walek <vwalek>
Component:	Release	Assignee:	Justin Pierce <jupierce>
Status:	CLOSED ERRATA	QA Contact:	Dongbo Yan <dyan>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, bleanhar, bparees, jokerman, mmccomas, smunilla, xiuwang
Target Milestone:	---
Target Release:	3.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-28 07:54:52 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 Vladislav Walek 2018-04-03 12:46:01 UTC

Description of problem:

when executing the build with jenkins pipeline, the latest jenkins-slave-maven-rhel7 image is pulled (currently as 3.9) even for the OCP version 3.6. Workaround would be to change the latest tag to the desired tag.
The latest image contains oc cli tools 3.9 which are causing the build issue (not compatible).

Also, when checking the default jenkins instance running on openshift, I see that there is no tag specified, so it will always use the latest one.

Version-Release number of selected component (if applicable):
Openshift Container Platform 3.6

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
now the jenkins pulls the latest image - not considering the version of OCP
- example - pulling version 3.9/latest on OCP version 3.6, where jenkins image contains different version of CLI tools (not compatible with actual version of OCP)

Expected results:
by default, the jenkins will get the tag same to the major release of openshift (e.g. 3.7 = image:3.7)

Additional info:
it could be up to admin of the jenkins to specify the correct tag, however, assuming in default configuration to always pull the latest image could cause more issues (especially when running different versions of OCP and images)

Comment 1 Ben Parees 2018-04-03 13:29:51 UTC

Yeah, the v3.9 jenkins image was improperly tagged as "latest"

Comment 2 Vladislav Walek 2018-04-03 13:44:31 UTC

So what is correct:

the latest will always point to the new release or jenkins should not use the latest but predefined tag?
How the v3.9 was improperly tagged as latest ? 
Which image should be pulled when using latest?

Comment 5 XiuJuan Wang 2018-04-27 02:44:06 UTC

Checked jenkins-2-rhel7, jenkins-slave-maven-rhel7, jenkins-slave-nodejs-rhel7 in registry.access registry.
latest tag point to v3.6.173.0.112
v3.6,v3.5 and v3.4 tags point to v3.6.173.0.112
Move this to verified.

Comment 7 errata-xmlrpc 2018-06-28 07:54:52 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2007