K8ssandra-operator are getting crashed when deploying the k8ssandra cluster together with medusa

[tajul]

Hi everyone,
I am happy join here and sorry asking for help on my very first meet.
I have been trying to deploy a simple k8ssandra cluster together with medusa in my eks cluster. The k8ssandra-operator, k8cluster were up and running just fine. But when I am trying to deploy k8ssandra cluster and medusa together then the running k8ssandra-operator got crashed with the following error:

2025-02-21T02:59:53.650Z        INFO    Initial token computation could not be performed or is not required in this cluster     
{"controller": "k8ssandracluster", "controllerGroup": "k8ssandra.io", "controllerKind": "K8ssandraCluster", "K8ssandraCluster": 
{"name":"xxx-db","namespace":"k8ssandra"}, 
"namespace": "k8ssandra", "name": "xxx-db", "reconcileID": "430398ac-d5b8-4c1b-b64e-2f3d8447361b",
 "K8ssandraCluster": {"xxx":"xxx-xx","namespace":"k8ssandra"}, 
"error": "cannot compute initial tokens: at least one DC has num_tokens >= 16"}

AND

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x173e4e7]

I tried with k8ssandra-operator version 1.21.1 and 1.20.2
cassandra version 4.0.1
kubernetes info

Client Version: v1.29.3-eks-ae9a62a
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.12-eks-2d5f260

k8ssandra-cluster manifest

apiVersion: k8ssandra.io/v1alpha1
kind: K8ssandraCluster
metadata:
  name: xxx-xx
spec:
  cassandra:
    serverVersion: "4.0.1"
    superuserSecretRef: 
        name: xxx-xxx-superuser
    datacenters:
      - metadata:
          name: datacenter1
        size: 1
        resources:
          requests:
            cpu: 500m
            memory: 1Gi
          limits:
            cpu: 1000m
            memory: 2Gi
        storageConfig:
          cassandraDataVolumeClaimSpec:
            storageClassName: efs-sc
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 5Gi
        config:
          jvmOptions:
            heapSize: 1Gi
        stargate:
          size: 1
          heapSize: 2Gi
          resources:
              requests:
                cpu: 100m
                memory: 1Gi
              limits:
                cpu: 500m
                memory: 4G
  
  medusa:
    containerImage:
      registry: docker.io
      repository: k8ssandra/medusa
      name: medusa
      tag: 0.23.0
      pullPolicy: IfNotPresent
    cassandraUserSecretRef: 
      name: xxx-xxx-superuser
    storageProperties:
      storageProvider: s3
      # apiProfile: default
      # host: "s3://arn:aws:s3:ap-northeast-x:xxxxxx:accesspoint/xxxx-xxxx-backup-s3-accesspoint/"
      concurrentTransfers: 1
      maxBackupAge: 1
      maxBackupCount: 2
      multiPartUploadThreshold: 10000000000000000
      bucketName: xxxx-xxxx-backup
      prefix: xxxx
      region: ap-northeast-x
      secure: true
      storageSecretRef:
        name: medusa-bucket-secret

I would appreciate any of your help.
Thank you so much.

[alexander]

This was solved with a clean re-install of the operator.

[tajul]

@alexander
Thank you so much and sorry for the delayed update.

To solve the above problem I had to set the purgeBackups of medusa to false.
medusa:
…
…
purgeBackups: false
The detail solution can be found below:

k8ssandra-operator crash when deploy k8ssandra cluster with medusa