Namespace stuck in Terminating due to Permission and User

[MonicaMagoniCom]

When I delete the rabbitmq namespace, it gets stuck in Terminating state due to some user and permission that cannot be deleted from message-topology-operator. From the describe of the user I see:
'failed to retrieve cluster from reference: Secret "rabbitmq-quorum-default-user" not found'

I saw an issue #324 which is fixed and it seems related to the same problem I have, but I'm using message-topology-operator version 1.13.0 and still experiencing the issue.

The only way to delete users and permission is to patch finalizers.

[Zerpet]

Could you provide some YAML and steps to reproduce this issue?

We test a similar scenario in our integration tests, and we don't observe this problem. YAML manifests and some steps would be incredibly helpful.

[MonicaMagoniCom]

---
apiVersion: rabbitmq.com/v1beta1
kind: User
metadata:
  name: admin
  namespace: rabbitmq-system-quorum
spec:
  rabbitmqClusterReference:
    name: rabbitmq-quorum
    namespace: rabbitmq-system-quorum
---

apiVersion: rabbitmq.com/v1beta1
kind: Permission
metadata:
  name: comelit-permission
  namespace: rabbitmq-system-quorum
spec:
  vhost: "/"
  userReference:
    name: "admin" 
  permissions:
    write: ".*"
    configure: ".*"
    read: ".*"
  rabbitmqClusterReference:
    name: rabbitmq-quorum
    namespace: rabbitmq-system-quorum
apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
  labels:
    app: rabbitmq-quorum
  finalizers: []
  name: rabbitmq-quorum
  namespace: rabbitmq-system-quorum
spec:
  replicas: 3
  image: rabbitmq:3.12.8-management
  service:
    type: ClusterIP
  persistence:
    storageClassName: standard
    storage: 5Gi
  resources:
    requests:
      cpu: 150m
      memory: 3Gi
    limits:
      cpu: 500m
      memory: 3Gi
  rabbitmq:
    additionalPlugins:
      - rabbitmq_management
      - rabbitmq_peer_discovery_k8s
      - rabbitmq_prometheus
    additionalConfig: |
      cluster_formation.peer_discovery_backend = rabbit_peer_discovery_k8s
      cluster_formation.k8s.host = kubernetes.default.svc.cluster.local
      cluster_formation.k8s.address_type = hostname
      cluster_formation.k8s.service_name = rabbitmq-test
      vm_memory_high_watermark.relative = 0.65
      cluster_formation.node_cleanup.interval = 10
      cluster_formation.discovery_retry_interval = 500
      cluster_partition_handling = autoheal
      queue_master_locator = min-masters
      loopback_users.guest = false
      disk_free_limit.absolute = 1GB
    advancedConfig: ""
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/component: rabbitmq-operator-quorum
    app.kubernetes.io/name: rabbitmq-cluster-operator-quorum
    app.kubernetes.io/part-of: rabbitmq-quorum
  name: rabbitmq-cluster-operator-quorum
  namespace: rabbitmq-system-quorum
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: rabbitmq-cluster-operator-quorum
  template:
    metadata:
      labels:
        app.kubernetes.io/component: rabbitmq-operator-quorum
        app.kubernetes.io/name: rabbitmq-cluster-operator-quorum
        app.kubernetes.io/part-of: rabbitmq-quorum
    spec:
      containers:
        - command:
            - /manager
          env:
            - name: OPERATOR_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: OPERATOR_SCOPE_NAMESPACE
              value: rabbitmq-system-quorum
          image: rabbitmqoperator/cluster-operator:2.7.0
          name: operator-quorum
          ports:
            - containerPort: 9782
              name: metrics
              protocol: TCP
          resources:
            limits:
              cpu: 200m
              memory: 100Mi
            requests:
              cpu: 50m
              memory: 100Mi
      serviceAccountName: rabbitmq-cluster-operator-quorum
      terminationGracePeriodSeconds: 10

[github-actions]

This issue has been marked as stale due to 60 days of inactivity. Stale issues will be closed after a further 30 days of inactivity; please remove the stale label in order to prevent this occurring.