Skip to main content

Repeated - "Attempted to load identical license, doing nothing" messages in redpanda logs

  • Updated

Summary

In Redpanda Self‑Managed clusters deployed with Redpanda Operator on Kubernetes, you may see repeated log messages similar to:

Attempted to load identical license, doing nothing: [Version: 0, Organization: <ORG>, Type: enterprise, Expiry(epoch): 1807834065]

This message is benign. It indicates that the Operator is re‑submitting a license Redpanda already has, and Redpanda is correctly ignoring the duplicate.

Environment

  • Redpanda Self‑Managed
  • Redpanda Operator (Kubernetes)
  • License configured via the Operator (enterprise.license or enterprise.licenseSecretRef) [Add license in K8s]

Symptoms

  • The Redpanda broker logs repeatedly contain entries like:Attempted to load identical license, doing nothing: [Version: 0, Organization: <ORG>, Type: enterprise, Expiry(epoch): <TS>]
  • Cluster behavior is otherwise normal: enterprise features remain enabled, and rpk cluster license info reports a valid license. [Check license with rpk]

Cause

  1. With Redpanda Operator, the license is specified in the Redpanda custom resource under spec.clusterSpec.enterprise.license or spec.clusterSpec.enterprise.licenseSecretRef. [Add license in K8s]
  2. The Operator reconciles the Redpanda resource every 1-3 minutes and on changes, and as part of reconciliation it re‑applies the license configuration. [Trigger license checks]
  3. Each reconciliation triggers an Admin API call to upload the license (PUT /v1/features/license). [Admin API put_license]
  4. Redpanda checks the uploaded license against the one already stored in its internal metadata. When they are identical, Redpanda does not replace the license and logs:Attempted to load identical license, doing nothing: [...]

The Operator currently does not pre‑check whether the license has changed before sending the update, so this pattern repeats every time the Operator reconciles.

Impact

  • No functional impact:The license already stored in Redpanda remains active.Enterprise features continue to work as expected.
  • The behaviour only results in extra log noise on the brokers.

Workaround / Recommended Action

  • No immediate action is required; the message is informational and safe to ignore as long as:
    rpk cluster license info shows a valid license, and there are no other license‑related warnings or violations. [Check license with rpk]
  • If the log noise is problematic in your environment. You can change logger admin_api_server to WARN instead of INFO.  

    The easiest is to set it on each broker via the following..    (you can set back to INFO or TRACE if want to debug issues in this area) 
     (note this is not persistent across broker restarts )
    rpk redpanda admin config log-level set admin_api_server  -l WARN   -e 0  --host localhost:9644 -X admin.tls.insecure_skip_verify=true
     

In future Redpanda Releases ... this log message will be change to DEBUG .. via PR 30188: admin: downgrade identical-license log from info to debug