Bug 2041888 - Intermittent incorrect build to run correlation, leading to run status updates applied to wrong build, builds stuck in non-terminal phases
Summary: Intermittent incorrect build to run correlation, leading to run status update...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Jenkins
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Gabe Montero
QA Contact: Jitendar Singh
URL:
Whiteboard:
Depends On:
Blocks: 2052063
TreeView+ depends on / blocked
 
Reported: 2022-01-18 13:14 UTC by Akram Ben Aissi
Modified: 2022-03-10 16:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:40:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift jenkins-sync-plugin pull 412 0 None Merged Bug 2041888: fix intermittent incorrect build to run correlation, leading to run status updates applied to wrong build, ... 2022-01-28 03:55:04 UTC
Github openshift jenkins pull 1375 0 None Merged Bug 2041888: bump openshift-sync to 1.0.53 2022-02-01 13:32:41 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:40:44 UTC

Description Akram Ben Aissi 2022-01-18 13:14:21 UTC
Description of problem:
intermittent incorrect build to run correlation, leading to run status updates applied to wrong build, builds stuck in non-terminal phases

Comment 14 errata-xmlrpc 2022-03-10 16:40:33 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.10.3 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-2022:0056


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