-
Bug
-
Resolution: Done
-
Major
-
None
-
ACM 2.8.0
-
False
-
None
-
False
-
-
-
Important
-
No
Description of problem: In the disconnected env, there are OCP 4 and OCP 311 managed clusters are managed by Hub. metric collector on the OCP 4 would forward metrics back to the Hub, but OCP 311 failed:
```
level=warn caller=logger.go:50 ts=2023-05-16T08:02:04.465590682Z component=forwarder component=metricsclient msg="error: failed to forward request happened at time: 5.883489053s"
level=warn caller=logger.go:50 ts=2023-05-16T08:02:10.35384366Z component=forwarder component=metricsclient msg="failed to forward request" err="Post \"https://observatorium-api-open-cluster-management-observability.apps.o4-disco2.disco.qe.red-chesterfield.com/api/metrics/v1/default/api/v1/receive\": dial tcp: lookup observatorium-api-open-cluster-management-observability.apps.o4-disco2.disco.qe.red-chesterfield.com on 10.0.29.181:53: server misbehaving"
```
this issue happens in the disconnected env, I sent the all access info to smeduri1@redhat.com and dbennett@redhat.com on Slack.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- In the disconnect Hub env, deploy MCOCR
- metrics collector is deployed and running on the OCP 311 managed cluster
- but metrics collector reports failed to forward requests.
Actual results:
Expected results:
Additional info:
- account is impacted by
-
ACM-5291 [ACM QE] Observability - ACM 2.8 Train 04 (Global Sprint 2023 - 05) QE Work Items
- Closed