Spinning up a VM here with two disks - one based on an image with

<http://harvesterhci.io/storageClassName=fast-replicas-3|harvesterhci.io/storageClassName=fast-replicas-3>

(provider Longhorn, selects disks in Longhorn with the “fast” tag) and one new volume with the same storageclass. It gets scheduled to node 5, while the volumes get attached to node 5 and 2 respectively, and the VM then fails to mount the volume that is attached to a different node. Is this a bug, or am I doing something obviously stupid?

Hi @big-judge-33880, could you generate the support-bundle for it? I thought that may be a bug. But need support-bundle to verify. Thanks!

I haven’t seen this again after recreating our storageclasses (the one used here had a misspelled “migratable” parameter because apparently nobody here is able to spell), but will certainly create an issue and attach a bundle if I see this again 👍