Bug 2048484 - SNO: cluster-policy-controller failed to start due to missing serving-cert/tls.crt
Summary: SNO: cluster-policy-controller failed to start due to missing serving-cert/tl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-controller-manager
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.10.0
Assignee: Filip Krepinsky
QA Contact: zhou ying
URL:
Whiteboard:
Depends On: 2045872
Blocks: 2049907
TreeView+ depends on / blocked
 
Reported: 2022-01-31 10:47 UTC by OpenShift BugZilla Robot
Modified: 2022-03-10 16:43 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2049907 (view as bug list)
Environment:
Last Closed: 2022-03-10 16:42:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-controller-manager-operator pull 596 0 None Merged [release-4.10] Bug 2048484: allow cluster-policy-controller to fallback to default cert 2022-01-31 22:10:24 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:43:08 UTC

Comment 1 Filip Krepinsky 2022-01-31 10:49:51 UTC 
@rfreiman backport for 4.10
Comment 3 Filip Krepinsky 2022-01-31 12:43:52 UTC 
@rfreiman all the jobs for 4.11 seems to be suceeding since the PR merged: https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-single-node-live-iso
Comment 10 errata-xmlrpc 2022-03-10 16:42:51 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.