Bug 1986562 - lastTriggeredImageId is populated in BuildConfig spec
Summary: lastTriggeredImageId is populated in BuildConfig spec
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.0
Assignee: Alice Rum
QA Contact: Jitendar Singh
Depends On:
TreeView+ depends on / blocked
Reported: 2021-07-27 19:03 UTC by Adam Kaplan
Modified: 2021-10-18 17:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-10-18 17:42:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift openshift-apiserver pull 239 0 None None None 2021-08-25 12:55:12 UTC
Github openshift openshift-controller-manager pull 193 0 None None None 2021-08-17 18:49:46 UTC
Github openshift origin pull 26411 0 None None None 2021-08-25 12:49:40 UTC
Github openshift origin pull 26432 0 None None None 2021-08-31 17:57:25 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:42:37 UTC

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:


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

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.


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