Bug 1890232 - Overwrite jenkins-agent-base imagestream
Summary: Overwrite jenkins-agent-base imagestream
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Samples
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Yaakov Selkowitz
QA Contact: XiuJuan Wang
Whiteboard: pre-merge-verified
Depends On: 1886890
TreeView+ depends on / blocked
Reported: 2020-10-21 17:51 UTC by OpenShift BugZilla Robot
Modified: 2021-01-22 07:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-12-14 13:50:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-samples-operator pull 333 0 None closed [release-4.6] Bug 1890232: Override jenkins-agent-base imagestream 2021-02-03 14:09:43 UTC
Red Hat Product Errata RHSA-2020:5259 0 None None None 2020-12-14 13:50:44 UTC

Description OpenShift BugZilla Robot 2020-10-21 17:51:29 UTC
+++ This bug was initially created as a clone of Bug #1886890 +++

Just like cluster-samples-operator already does for Jenkins itself and the Node.js and Maven agents, it should also overwrite the jenkins-agent-base imagestream so that users always get an image corresponding to their release of OpenShift.

Comment 1 Gabe Montero 2020-10-22 18:23:57 UTC
The bots have created PR https://github.com/openshift/cluster-samples-operator/pull/333 for this one but it won't be associated with this BZ until the master branch bz is verified by QA

Comment 4 XiuJuan Wang 2020-11-27 02:20:41 UTC
jenkins-agent-base imagestream has been integrated into openshift project in 4.6.0-0.nightly-2020-11-26-191112 cluster.

Comment 7 errata-xmlrpc 2020-12-14 13:50:18 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 (Moderate: OpenShift Container Platform 4.6.8 security and bug fix update), and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.