Can't add nvme disk through web GUI?

SUSE Virtualization
1

Trying to test a few things with Longhorn v2 and having a problem, Harvester 1.7.1.

I have a 1tb sata for the OS, I also gave the rest of that disk to Longhorn v1 for storage.

I have a 1tb nvme that I was hoping to set up as Longhorn v2.

When I edit the configuration for the host, click storage and scroll down to click on add disk, it says no disks found (something to that affect). If during the installer I select the nvme disk, Longhorn v1 is happy to use them for storage.

What am I doing wrong? Do I need to take each host offline before setting this up?

Sorry for the newb questions, there will probably be a few more as I try to learn this product (and Rancher and Kubernetes).

2

Looks like I need to partition and format as ext4 before Harvester can see the disk. Would really be nice if this could be detected in the web gui and handled without having to ssh in and fdisk to get the disk prepared.

3

So here’s what happened. I ended up booting to a gparted rescue disk to take a look. Both disks had been dedicated to LH v1, but thinking this was an error from previous installs, I formatted the nvme back to a clean ext4. Boot back into Harvester, went through setting up LH v2 on the nvme, and went back to look at each host because I still had a warning. Turns out now the storage part of the sata disk is offline. The error is that the uuid of the LH v1 disk does not match the one on disk. So I wiped that out trying to clear the nvme for use on LH v2.

This explains why it was not visible when I was trying to set LH v2 up before the wipe.

It seems that even when you say to use part of the OS disk, if the installer sees another disk, it’s going to use it. I think I need to wipe this out, physically remove the nvme disk, install Harvester and use the OS disk for storage, then physically add the nvme disk back into the computer.

I know LHv2 is still “experimental”, when it hits preview or production I hope there is a better way to handle these things. There is probably a way to handle this through a terminal, but through the GUI would be more friendly.