Describe the Bug

Robot test case Test Longhorn Volume Recovery fails on master-head (longhorn-manager 94237fc) and v1.12.x-head (longhorn-manager f57c766) with v2 volumes.

After the instance manager is deleted and restarted, the v2 volume is unable to recover to Healthy state but gets stuck in Degraded state:

https://ci.longhorn.io/job/private/job/longhorn-e2e-test/8082/console

To Reproduce

Run robot test case Test Longhorn Volume Recovery:

-t \"Test Longhorn Volume Recovery\" -v RETRY_COUNT:259200 -v DATA_ENGINE:v2

Expected Behavior

N/A

Support Bundle for Troubleshooting

supportbundle_e8fec899-f882-4469-b93b-9de47bb64bd8_2026-05-27T06-17-18Z.zip

Environment

• Longhorn version: master-head, v1.12.x-head
• Impacted volume (PV):
• Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
• Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.35.4+k3s1
  • Number of control plane nodes in the cluster:
  • Number of worker nodes in the cluster:
• Node config
  • OS type and version: sles 16.0
  • Kernel version:
  • CPU per node:
  • Memory per node:
  • Disk type (e.g. SSD/NVMe/HDD):
  • Network bandwidth between the nodes (Gbps):
• Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
• Number of Longhorn volumes in the cluster:

Additional context

No response

Workaround and Mitigation

No response