IDE Services Requires Re-activation After PostgreSQL Database Migration

Problem

After migrating the PostgreSQL database used by an IDE Services deployment, the instance requested re-activation.

Activation attempts failed with errors such as:

• We couldn't find a JetBrains IDE Services license available for activation.
• Invalid token, server key does not match.
• LicenseValidationService reported No valid license found.

The IDE Services pods themselves were running and healthy.

Cause

The IDE Services deployment had been migrated to a different PostgreSQL database.

IDE Services server pods are stateless. Persistent application state is maintained using PostgreSQL and object storage, and multiple IDE Services server replicas can use the same database and object storage.

IDE Services activation is associated with a unique server identifier.

Replacing the database caused the deployment to require a new activation, while the existing license activation still needed to be reset.

Resolution

1. Contact JetBrains Support and request an activation reset for the affected IDE Services license.
2. After the activation is reset, activate the IDE Services instance again.
3. Verify that IDEs can successfully obtain licenses from the instance.

Recommendation

Recreating or restarting IDE Services pods should not require re-activation as long as they continue to use the same PostgreSQL database/schema and object storage, because the server pods are stateless.

If the PostgreSQL database is recreated, replaced, or migrated to a new database, the IDE Services instance may require re-activation. If the existing activation prevents the new instance from being activated, contact JetBrains Support to reset it. See Cannot activate instance after database re-creation: Public key mismatch