Bug 1518501
Summary: | Builds failing after new Red Hat jenkins images updated | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jaspreet Kaur <jkaur> |
Component: | Build | Assignee: | Ben Parees <bparees> |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | urgent | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.0 | CC: | aos-bugs, bparees, gmontero, jialiu, jlee, jokerman, mmccomas, pep, rhowe, xiuwang, xtian |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Jenkins images that were not backwards compatible to older clusters were pushed as "latest".
Consequence: Clusters which referenced jenkins master+slave images via the latest tag picked up images which might not be compatible with the cluster, due to the version of the oc client binary embedded in the jenkins images. This results in oc client operations failing when run from within the jenkins(and jenkins slave) containers, against the cluster.
Fix: The latest tag now points to a compatible image that will work with older clusters.
Result: Older clusters referencing the "latest" jenkins images will work again.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-18 13:24:28 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
Jaspreet Kaur
2017-11-29 05:49:47 UTC
Security team due to: User "system:serviceaccount:cipe-develop:jenkins" cannot create template.openshift.io.processedtemplates in project "cipe-develop" (Jenkins SA should have edit permissions in the project). 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-2017:3464 |