Bug 1752744 - kube-scheduler-operator target is (0/0 up)
Summary: kube-scheduler-operator target is (0/0 up)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.3.0
Assignee: Maciej Szulik
QA Contact: zhou ying
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-17 06:57 UTC by Junqi Zhao
Modified: 2020-01-23 11:06 UTC (History)
3 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:06:39 UTC

Comment 1 Junqi Zhao 2019-09-26 09:08:32 UTC 
no issue with 4.2.0-0.nightly-2019-09-25-233506 now
Comment 2 Maciej Szulik 2019-09-26 10:15:55 UTC 
The fixes from https://bugzilla.redhat.com/show_bug.cgi?id=1749457 might addressed this issue as well.
Moving to modified in that case, and based on previous comment.
Comment 7 errata-xmlrpc 2020-01-23 11:06:16 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, 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-2020:0062
Note You need to log in before you can comment on or make changes to this bug.