Bug 1749457
| Summary: | Clusters must report a metric on whether masters are schedulable to telemetry | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> | ||||
| Component: | kube-scheduler | Assignee: | Mike Dame <mdame> | ||||
| Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.2.0 | CC: | aos-bugs, maszulik, mdame, mfojtik | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-10-16 06:40:33 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Clayton Coleman
2019-09-05 16:14:59 UTC
Failed to verify with 4.2.0-0.nightly-2019-09-11-202233, open console, search "cluster_master_schedulable" in "Insert Metric at Cursor", there is not this item, feel free to contact with me if there is misunderstanding. thx no, checked with 4.2.0-0.nightly-2019-09-15-221449, still have not fix. Created attachment 1618351 [details]
cluster-master-schedulable
Looking today I am able to see the cluster-master-schedulable metric on a running cluster (4.2.0-0.ci-2019-09-23-093016)
Verified with 4.2.0-0.nightly-2019-09-24-025718 cluster_master_schedulable https 10.129.0.11:8443 metrics openshift-kube-scheduler-operator openshift-kube-scheduler-operator-757465cc56-g8btl metrics 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-2019:2922 |