cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Tenant id is unknown

NikleshThakur
Visitor

Hi All,

We are migrating oneagent traffic from one environment to another environment under the same managed cluster. 

Connectivity is opened  to new environment activegate.

We are using oneagentctl command line to change the configuration to new environment. 

./oneagentctl --set-server= https://example.co.com:9999;https://198.0.0.0:9999 --set-tenant=<new env tenant id> --set-tenant-token=<new env tenant token> --restart-service

Communication has been changed to new environment activegate but traffic is not reporting. Also, traffic is not reporting to old env. 

Getting below error in the logs, Tenant id is unknown. 


2023-03-06 16:36:16.136 UTC [702f77e5] warning [native] Unable to send/handle initial setup request: received message with error code: REQUEST_REJECTED - sender's message: UnknownTenantFilter: Tenant id is unknown (26ms)
2023-03-06 16:36:16.142 UTC [702f77e5] warning [native] Unable to send/handle initial cluster time request: received message with error code: REQUEST_REJECTED - sender's message: UnknownTenantFilter: Tenant id is unknown (5ms 

Any idea why tenant is not changed or am I missing something here

 

Niklesh 

4 REPLIES 4

Mohamed_Hamdy
DynaMight Champion
DynaMight Champion

Hi NikleshThakur,

based on the retrieved error, make sure that you've added the correct tenant id and token. also, if it's in full-stack monitoring you need to restart the processes after it's migrated successfully and you will see a message on the processes after the migration but this is not your case now.

Certified Dynatrace Professional | Certified Dynatrace Services Delivery - Observability & CloudOps | Dynatrace Partner - yourcompass.ca

Hi Mohamed,

Thanks for your response. 

Yes, we are verifying the commands and will execute the commands individually.

Hi Niklesh,
First make sure You don't have errors in token or connection endpoints (server/ag) please paste parameters from Your APIv1: /api/v1/deployment/installer/agent/connectioninfo - You can use GUI on APIv1 => deployments to get them
In response there You will find proper tenantID, token and connection endpoints.
I don't see a reason for it to not work if all parameters are valid.

dannemca
DynaMight Guru
DynaMight Guru

Not sure if was a typo during copy/paste, but there is a space after --set-server=. Try to remove this space and check.

./oneagentctl --set-server=https://example.co.com:9999;https://198.0.0.0:9999 --set-tenant=<new env tenant id> --set-tenant-token=<new env tenant token> --restart-service

Also, can you confirm that new config was really applied, checking with --get-server , --get-tenant and  --get-tenant-token params?

Site Reliability Engineer @ Kyndryl

Featured Posts