Bug 1854919 - CI builds are using outdated location with signing keys
Summary: CI builds are using outdated location with signing keys
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: config-operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Stefan Schimanski
QA Contact: Xingxing Xia
Depends On:
Blocks: 1854960
TreeView+ depends on / blocked
Reported: 2020-07-08 12:45 UTC by Vadim Rutkovsky
Modified: 2020-10-27 16:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1854960 (view as bug list)
Last Closed: 2020-10-27 16:13:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-update-keys pull 17 0 None closed Update CI search location to match where release signer publishes 2020-07-08 12:45:36 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:13:30 UTC

Description Vadim Rutkovsky 2020-07-08 12:45:36 UTC
The official URL for CI builds is gs://openshift-ci-release/releases/... to distinguish CI signing from OCP signing

Comment 1 Vadim Rutkovsky 2020-07-08 13:43:50 UTC
Verified 4.6.0-0.ci-2020-07-08-041445 -> 4.6.0-0.ci-2020-07-08-121445 update, https://storage.googleapis.com/openshift-ci-release/releases/signatures/openshift/release bucket was used in CVO

Comment 4 errata-xmlrpc 2020-10-27 16:13:10 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.6 GA Images), 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.