Bug 1986562

Summary:	lastTriggeredImageId is populated in BuildConfig spec
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	Build	Assignee:	Alice Rum <irum>
Status:	CLOSED ERRATA	QA Contact:	Jitendar Singh <jitsingh>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.9	CC:	aos-bugs
Target Milestone:	---
Target Release:	4.9.0
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:	2021-10-18 17:42:20 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 Adam Kaplan 2021-07-27 19:03:25 UTC

Description of problem:

When a build is started via an ImageChange trigger, the lastTriggeredImageId is populated/updated in BuildConfig spec. This is deprecated behavior that should not occur in OCP 4.9.


Version-Release number of selected component (if applicable): 4.9


See also:

https://issues.redhat.com/browse/BUILD-188

Comment 9 Jitendar Singh 2021-09-09 14:55:13 UTC

VERIFIED
==================

Comment 11 errata-xmlrpc 2021-10-18 17:42:20 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.9.0 bug fix and security 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.

https://access.redhat.com/errata/RHSA-2021:3759