longhorn: [BUG] longhorn RWX doesn't work on freshly created volume

Describe the bug (🐛 if you encounter this issue)

I made a new Longhorn RWX volume. The pods that reference it fail to start.

To Reproduce

---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: rwx
  name: rwx
  namespace: wordpress
spec:
  replicas: 2
  selector:
    matchLabels:
      app: rwx
  strategy: {}
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: rwx
    spec:
      containers:
      - image: nginx:latest
        name: nginx
        resources: {}
        volumeMounts:
        - mountPath: /data
          name: data
      volumes:
      - name: data
        persistentVolumeClaim:
          claimName: rwx
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: rwx
  namespace: wordpress
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Gi
  storageClassName: longhorn-rwx
---
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: longhorn-rwx
parameters:
  fromBackup: ""
  migratable: "true"
  numberOfReplicas: "3"
  recurringJobSelector: '[{"name":"backup","task":"backup","cron":"5 0 * * *","retain":14}]'
  staleReplicaTimeout: "2880"
provisioner: driver.longhorn.io
reclaimPolicy: Delete
volumeBindingMode: Immediate

Expected behavior

My pods work with the rwx volume I want.

Support bundle for troubleshooting

Too big for GitHub, but now here as of this edit: support bundle

Environment

• Longhorn version: 1.5.1
• Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Helm through an ArgoCD Application
• Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: k3s 1.27.3
  • Number of management node in the cluster: 5
  • Number of worker node in the cluster: 0
• Node config
  • OS type and version: Almalinux 9.2
  • Kernel version: 5.14.0-284.25.1.el9_2.x86_64
  • CPU per node: 16
  • Memory per node: 64 GB
  • Disk type(e.g. SSD/NVMe/HDD): NVMe OS, SSD for Longhorn Data
  • Network bandwidth between the nodes: 2.5 Gbps
• Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal
• Number of Longhorn volumes in the cluster: 45

Additional context

The ArgoCD application that installed longhorn:

---
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  annotations:
    argocd.argoproj.io/sync-wave: "1"
  finalizers:
    - resources-finalizer.argocd.argoproj.io
  name: longhorn
  namespace: argocd
spec:
  destination:
    namespace: longhorn-system
    server: 'https://kubernetes.default.svc'
  ignoreDifferences:
    - group: apps
      kind: Deployment
      name: longhorn-admission-webhook
    - group: apps
      kind: Deployment
      name: longhorn-conversion-webhook
    - group: apps
      kind: Deployment
      name: longhorn-recovery-backend
  project: default
  source:
    chart: longhorn
    helm:
      releaseName: longhorn
      values: |
        csi:
          kubeletRootDir: "/var/lib/kubelet"
        defaultSettings:
          backupTarget: "s3://longhorn@us-east-1/"
          backupTargetCredentialSecret: "longhorn-minio-creds"
          defaultDataLocality: "best-effort"
          replicaAutoBalance: "best-effort"
        longhornAdmissionWebhook:
          replicas: 0
        longhornConversionWebhook:
          replicas: 0
        longhornManager:
          log:
            format: json
        longhornRecoveryBackend:
          replicas: 0
        persistence:
          defaultDataLocality: "best-effort"
          defaultReplicaAutoBalance: "best-effort"
          migratable: true
          recurringJobSelector:
            enable: true
            jobList: '[{"name":"backup","task":"backup","cron":"5 0 * * *","retain": 14}]'
    repoURL: 'https://charts.longhorn.io'
    targetRevision: "*"
  syncPolicy:
    automated:
      prune: true
      selfHeal: true