Remote Health not able to send data in OpenShift Container Platform 4

Solution Verified - Updated -

Issue

  • The telemeter-client pod is unable to send data from Remote Health and is reporting the below error.

    level=error caller=forwarder.go:268 ts=2021-10-21T09:47:42.331892567Z component=forwarder/worker msg="unable to forward results" err="unable to authorize to server: unable to exchange initial token for a long lived token: 409:\nthe provided cluster identifier is already in use under a different account or is not sufficiently random\n"
    level=error caller=forwarder.go:268 ts=2021-10-21T09:48:42.705282117Z component=forwarder/worker msg="unable to forward results" err="unable to authorize to server: unable to exchange initial token for a long lived token: 409:\nthe provided cluster identifier is already in use under a different account or is not sufficiently random\n"
    level=error caller=forwarder.go:268 ts=2021-10-21T09:49:43.185979673Z component=forwarder/worker msg="unable to forward results" err="unable to authorize to server: unable to exchange initial token for a long lived token: 409:\nthe provided cluster identifier is already in use under a different account or is not sufficiently random\n"
    

Environment

  • Red Hat OpenShift Container Platform 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content