Error when creating token - DatastoreConfig kms-datastore doesnt exists or not initialized yet

Google Cloud Apigee
,
1

I have the Apigee private cloud deployment with 4.53.00 version and the installation is completed. When creating the token for an API Proxy of an environment getting the error as below,

{“ErrorCode”: “invalid_client, “Error”: “DataStoreConfig kms-datastore doesn’t exist or not initialized yet”}

But based on the servers list API (mgmturl/v1/servers?pod=external&region=dc1), I could see all the three cassandra nodes are added to it with type,

[cache-datastore, kms-datastore,dc-datastore,keyvaluemap-datastore,counter-datastore]

Tried restarting the MP and Routers. The same is working in other environments within the same installation. How do I resolve this issue now ?

@dchiesa1 - Any thoughts ?

2

Resolved it. Actually it was missing the datastores in the dc-2 which was causing this. Once I added the servers to the dc-2 pod it started working. Missed it while performing the datastore addition.

But, should this automatically happen when creating a new pod ? Why do we have to do this manually.

1 Like
3

Hey @johnwilliams, thanks for sharing your solution. We’ve noted your question and will keep it on our radar.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

6

The issue occurred because the kms-datastore was missing in the dc-2 pod, causing token creation to fail despite the other nodes being visible. Adding the missing datastores to dc-2 resolved the problem. This doesn’t happen automatically when creating a new pod; datastore configuration must be manually added for each pod, which is why the error appeared.