KOTS Admin Console Login Hangs Due to Excessive Version History Sequences

Benjamin Lutz
Benjamin Lutz
  • Updated

Published Date: April 10, 2026
Validated: Yes
Audience: Everyone
Products and Versions Covered: 

  • Jama Connect® version(s): 
  • Self-hosted

Summary

  • Logging in to the KOTS Admin Console results in an indefinite spinner after entering the correct password.

  • kubectl kots commands can take up to 20 minutes to complete.

Resolution

This behavior was likely due to an excessive accumulation of KOTS application sequences (hundreds of Version History entries), which can significantly degrade performance and cause the KOTS Admin Console to appear unresponsive during login.

Remove Excessive Sequences by Reinstalling the Application (KOTS CLI)

  1. Backup the KOTS config

    kubectl kots get config --current --decrypt > config.yaml

  2. Uninstall the Jama Connect® application using the KOTS CLI.

    kubectl kots remove jama-k8s -n default -f

  3. Reinstall/deploy the application using the KOTS CLI.

    kubectl kots install jama-k8s/standardkots --app-version-label=<app version> --namespace default --license-file /path/to/<license>.yaml  --config-values /path/to/config.yaml

To prevent the issue from happening again, go to the KOTS Admin Console, select the 'Version history' tab, and set 'Configure automatic updates' to 'Never'.  This will prevent a buildup of unnecessary sequences over time. 

Additional Resources

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement 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.