Bug 1632983
Summary: | [3.11] metrics API Proxy endpoint is deprecated in metrics.go | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
Component: | oc | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.11.0 | CC: | anli, aos-bugs, dmoessne, jokerman, lmeyer, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
The location of the master proxy API changed.
Consequence:
Since the MetricsApiProxy diagnostic uses this endpoint, it broke.
Fix:
The diagnostic was updated to look at the correct endpoint.
Result:
It should now work as expected.
|
Story Points: | --- |
Clone Of: | 1571176 | Environment: | |
Last Closed: | 2019-01-30 15:19:31 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: | |||
Bug Depends On: | 1571176 | ||
Bug Blocks: |
Comment 1
Junqi Zhao
2018-09-26 02:10:52 UTC
Not a 3.11.0 release blocker; moving to 3.11.z. Issue is fixed # oc adm diagnostics MetricsApiProxy [Note] Determining if client configuration exists for client/cluster diagnostics Info: Successfully read a client config file at '/root/.kube/config' Info: Using context for cluster-admin access: 'default/ip-172-18-1-52-ec2-internal:8443/system:admin' [Note] Running diagnostic: MetricsApiProxy Description: Check the integrated heapster metrics can be reached via the API proxy [Note] Summary of diagnostics execution (version v3.11.69): [Note] Completed with no errors or warnings seen. # openshift version openshift v3.11.69 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:0096 |