Bug 2090000 - Cluster Network Operator stuck in CrashLoopBackOff when scheduled to same master
Summary: Cluster Network Operator stuck in CrashLoopBackOff when scheduled to same master
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.8.z
Assignee: Andreas Karis
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 2083079
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-24 23:41 UTC by OpenShift BugZilla Robot
Modified: 2023-09-15 01:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 18:23:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1457 0 None open [release-4.8] [release-4.10] Bug 2090000: Reserve port TCP/9104 for cluster-network-operator 2022-05-26 14:17:38 UTC
Red Hat Product Errata RHBA-2022:4952 0 None None None 2022-06-16 18:23:57 UTC

Comment 6 errata-xmlrpc 2022-06-16 18:23:49 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.8.43 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.

https://access.redhat.com/errata/RHBA-2022:4952

Comment 7 Red Hat Bugzilla 2023-09-15 01:55:10 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days


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