This message was deleted.
# harvestera
adamant-kite-43734
03/21/2024, 11:53 AMThis message was deleted.
b
bland-article-62755
03/21/2024, 3:15 PMTry to detach the disk from harvester3 and turn the VM on again.
bland-article-62755
03/21/2024, 3:16 PMEven though it might be RWX mode, there might be something blocking it from attaching to the VM's pod.
bland-article-62755
03/21/2024, 3:16 PM(at least that's where I'd start)
r
rhythmic-article-81903
03/21/2024, 3:54 PMI have done that. Also deleted disk and created new one. I can schedule VM on harverster1 without issues, but when I add this nvme disk it fails. For some weird reason harvester wants to schedule it everywhere else than where it should go.
b
bland-article-62755
03/21/2024, 3:57 PMYou're adding an additional disk, or setting a new boot disk?
r
rhythmic-article-81903
03/21/2024, 3:57 PMadditional disk
b
bland-article-62755
03/21/2024, 3:58 PMhmmm
bland-article-62755
03/21/2024, 3:58 PMAnything in events or logs from the UI?
r
rhythmic-article-81903
03/21/2024, 4:04 PMonly that failure to mount disk
rhythmic-article-81903
03/21/2024, 5:20 PMI now even tried that I disable V2 on all other nodes. Still not scheduling on the right node...
b
bland-article-62755
03/21/2024, 5:21 PMYou can try changing this:
r
rhythmic-article-81903
03/21/2024, 5:26 PMit is not supported for V2
b
bland-article-62755
03/21/2024, 5:27 PMI'm out of ideas. ¯\_(ツ)_/¯
r
rhythmic-article-81903
03/21/2024, 6:10 PMThis is what longhorn shows and tries to do
rhythmic-article-81903
03/21/2024, 6:10 PMThis is shown in node
rhythmic-article-81903
03/21/2024, 6:10 PMso something is off...
rhythmic-article-81903
03/21/2024, 6:29 PMOkay. Having migratable=False in storage class causes this problem