Failed to send agent registration request + Status: 401 Unauthorized

[Raghavendar_Rao]

Hi,

I am running into following issue when I try to monitor my k8s cluster using Appdynamics. I verified that my controller key is correct. Any other reason why I would run into this issue?

Thanks,

Raghu

[WARNING]: 2021-01-16 05:27:39 - agentregistrationmodule.go:352 - dev is not a valid namespace in your kubernetes cluster
[INFO]: 2021-01-16 05:27:39 - agentregistrationmodule.go:356 - Established connection to Kubernetes API
[INFO]: 2021-01-16 05:27:39 - agentregistrationmodule.go:68 - Cluster name: TEST
[INFO]: 2021-01-16 05:27:39 - agentregistrationmodule.go:119 - Initial Agent registration
[ERROR]: 2021-01-16 05:27:39 - agentregistrationmodule.go:131 - Failed to send agent registration request: Status: 401 Unauthorized, Body:
[ERROR]: 2021-01-16 05:27:39 - agentregistrationmodule.go:132 - clusterId: -1
[ERROR]: 2021-01-16 05:27:39 - agentregistrationmodule.go:134 - Registration properties: {}

[iamryan]

Hi @sajo.sam,

I did some digging and found this info.

We can see 401 when there is an issue either in the access key or in the account name
 

kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key="myaccount access key valid"

Can you please check and confirm if the access key you have used to create the secret is same with the access key under Settings#licenses#Account.
 
If not the same then please pass the same and repeat the steps of creating a secret and create yaml .

[iamryan]

Hi @Paul.Gilbody,

Can you share the solution here? Knowledge sharing is a key factor to the success of the community. 

[Paul_Gilbody]

Thanks Ryan - yes already had done.   Resolved now.

[sajo_sam]

Hi @Paul.Gilbody ,
Can you share the solution here. I'm stuck with same issue

[iamryan]

Hi @Paul.Gilbody,

Given how old this conversation is with no answer, it might be best to contact support or your AppD Rep for this issue. 

How do I submit a Support ticket? An FAQ 

[Paul_Gilbody]

I am having the same issue following an upgrade on OpenShift from the old operator (0.6.11) to v22.11

[srikanth_kagith]

Hi @Raghavendar Rao.Kota,

Did you ever happen to find a fix for this?

^ Posted edited by @Ryan.Paredez to tag the original author

[iamryan]

Hi @Raghavendar Rao.Kota ,

There is an existing community post that looks related, please have a look and let me know if it helped. 

Kubernetes install 

[Raghavendar_Rao]

Hi Ryan,

Thanks for the response. I followed the link provided in that post, but still see the issue.

Regards,

Raghu

[iamryan]

Hi @Raghavendar Rao.Kota,

Thanks for letting me know. Let's see if the community can jump in and help. If you happen to find any new information or a solution, please come back and share it as a reply to this post.