Bug 1911181

Created attachment 1742508 [details]
telemeter-client deploy file

Description of problem:
IPI_GCP cluster, "write limit reached for cluster" error shows only one time, and no such error later
# oc -n openshift-monitoring logs $(oc -n openshift-monitoring get po | grep telemeter-client | awk '{print $1}') -c telemeter-client
level=info caller=main.go:85 ts=2020-12-28T04:02:12.273623216Z msg="telemeter client initialized"
level=warn caller=forwarder.go:130 ts=2020-12-28T04:02:12.273836401Z component=forwarder msg="not anonymizing any labels"
level=info caller=main.go:259 ts=2020-12-28T04:02:12.536773019Z msg="starting telemeter-client" from=https://prometheus-k8s.openshift-monitoring.svc:9091 to=https://infogw.api.openshift.com/ listen=localhost:8080
level=warn caller=forwarder.go:130 ts=2020-12-28T04:02:16.449297073Z component=forwarder msg="not anonymizing any labels"
level=error caller=forwarder.go:268 ts=2020-12-28T04:02:17.0623242Z component=forwarder/worker msg="unable to forward results" err="gateway server reported unexpected error code: 429: write limit reached for cluster with id \"e2a400ae-794a-4f9b-b93d-b3f961286529\"\n"


# oc get clusterversion/version -o jsonpath="{.spec.clusterID}"
e2a400ae-794a-4f9b-b93d-b3f961286529

Version-Release number of selected component (if applicable):
4.7.0-0.nightly-2020-12-21-131655

How reproducible:
sometimes

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: