Bug 2061554 - [release-4.10] Add extra debug information to image signature workflow test
Summary: [release-4.10] Add extra debug information to image signature workflow test
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Adam Kaplan
QA Contact: Jitendar Singh
Depends On: 2057990
Blocks: 2063284 2064800
TreeView+ depends on / blocked
Reported: 2022-03-07 20:01 UTC by OpenShift BugZilla Robot
Modified: 2022-05-30 09:32 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-21 12:40:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26889 0 None open [release-4.10] Bug 2061554: Add debug info for signature test 2022-03-07 20:02:13 UTC
Red Hat Product Errata RHBA-2022:0928 0 None None None 2022-03-21 12:40:51 UTC

Comment 4 Priti Kumari 2022-03-16 09:46:02 UTC
@adam.kaplan What I understood from whole conversation and https://bugzilla.redhat.com/show_bug.cgi?id=2057990#c4 is we still trying to figure out the reason for failure but adding some additional debug information to understand the `ca` error more clearly. We want to backport it to 4.9 and observe the behavior. Correct me if I am wrong. 

If this is the case I need to keep the original issue open and mark this verified. Looking for your response.

Comment 5 Adam Kaplan 2022-03-16 15:04:59 UTC
That is correct - the current BZ is backporting the extra debugging, since no other jobs seem to have this issue.

I would copy the original BZ so that we have a record for the initial issue.

Comment 6 Priti Kumari 2022-03-17 05:41:09 UTC

Comment 8 errata-xmlrpc 2022-03-21 12:40:36 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 (OpenShift Container Platform 4.10.5 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.