Chrome pod 401 error when running Private Synthetic Agent 22.9.0 on AKS cluster

[PsychicMushroom]

Hi Guys,

We are running AKS with CNI plugin with Synthetic Sever(Azure VM) and getting the below errors in the Chrome pod logs.   Private Synthetic Agent version is 22.9.0

It's as though Chrome pod is unable to authenticate with heimdall, hence the 401 error. Has anyone seen this before?  Not sure how to deal with this issue.

INFO 2023-05-31 04:32:59,176 ad.internal idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
Creating directory: ../temp/customScreencasts
INFO 2023-05-31 04:32:59,176 ad.internal idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
Creating directory: ../temp/pageScreencasts
INFO 2023-05-31 04:32:59,176 ad.internal.HeimdallClient idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
ERROR 2023-05-31 04:32:59,188 ad.internal.HeimdallClient idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 failed Received status code: 401. Time taken for api call in ms: 0
ERROR 2023-05-31 04:32:59,189 ad.internal idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 failed Received status code: 401. Time taken for api call in ms: 0
Traceback (most recent call last):
File "driver.py", line 79, in <module>
measurement_data = heimdall_client.fetchMeasurement(MEASUREMENT_ID)
File "/app/agent/Client/heimdall_client.py", line 73, in fetchMeasurement
raise HeimdallClientException(errorMessage)
customExceptions.HeimdallClientException: Fetching measurement for id: 4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513 failed Received status code: 401. Time taken for api call in ms: 0
INFO 2023-05-31 04:32:59,189 ad.internal.ResultsUploader idx-measurementId=4a8f5e61-08ee-43da-a2e1-b719b8efa620~81527f82-7801-469c-83da-e9a4d504b513
Uploading artifacts

[Noopur_Tibdiwal]

@Michael.Lee  : If the issue is not already resolved it's best if you create a Support ticket for end to end review of agent setup.

You may also refer -

https://community.appdynamics.com/t5/Knowledge-Base/How-do-I-debug-common-Linux-Private-Synthetic-Ag...

How do I submit a Support ticket? An FAQ 

Regards,

Noopur