Jama Connect Issue After License Change: “Tenant ‘jama’ Has Not Been Initialized” (KOTS)

Kellen Fields
Kellen Fields
  • Updated

Published Date: March 10, 2026

Validated: Yes

Audience: Everyone

Products and Versions Covered:

  • Self-hosted, Replicated - KOTS

Summary 

Symptoms

After updating or changing the Jama Connect license in a self-hosted Replicated (KOTS) environment, Jama Connect may become unavailable and display errors such as:

  • java.lang.IllegalStateException: Your instance of Jama Cloud is being upgraded! Please check later.
  • API/log error: Tenant "jama" has not been initialized.

Cause

This issue can occur when the tenant-manager Kubernetes Job becomes stuck and prevents the core pod from restarting cleanly after the license change.

In some cases, the underlying trigger is an attempted patch/redeploy while the tenant-manager Job is still running (for example, a double deployment). Kubernetes Jobs have immutable fields (such as spec.template), so a second deployment attempt can fail with errors like:

  • UPGRADE FAILED: cannot patch "tenant-manager" with kind Job: Job.batch ... spec.template ... is immutable

Resolution 

Step 1: Delete the conflicting KOTS resources

On the application server, run the following command to remove the stuck/conflicting resources:

kubectl delete sts/core sts/hazelcast sts/activemq job/tenant-manager

## Note: in v9.28.x and above there are two, new jobs that will attempt to start up.
## Removing the activemq statefulset will interfere with their normal operations 
## After redeployment, you'll need to monitor for and remove the following:
kubectl delete job activemq-backup
kubectl delete job activemq-restore

Step 2: Re-deploy from the KOTS Admin Console

Re-deploy the application using the KOTS Admin Console (deploy the latest saved configuration/sequence). This allows KOTS to recreate the deleted resources cleanly and re-run tenant provisioning steps.

Step 3 (Optional): Confirm the tenant-manager behavior

The tenant-manager Job is expected to run during deployment/upgrade activities and then terminate when complete. If it does not terminate, that’s a sign it may be stuck and blocking progress.

Additional Resources

Feedback: We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

 

 

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.