[ovirt-users] Re: oVirt Node 4.4.2 is now generally available

On Sat, Oct 3, 2020 at 4:06 PM Amit Bawer <abawer(a)redhat.com&gt; wrote: Yes, it is so This is a testbed NUC I use for testing. It has 2 disks, the one named sdb is where ovirt node has been installed. The one named sda is where I configured gluster though the wizard, configuring the 3 volumes for engine, vm, data The filter that you do have in the 4.4.2 screenshot should correspond to Yes it is so. Of course it works only in 4.4.0. In 4.4.2 there is no special file created of type /dev/disk/by-id/.... See here for udevadm command on 4.4.0 that shows sdb3 that is the partition corresponding to PV of root disk https://drive.google.com/file/d/1-bsa0BLNHINFs48X8LGUafjFnUGPCsCH/view?us... Here lsblk as seen by 4.4.0 with gluster volumes on sda: https://drive.google.com/file/d/1Czx28YKttmO6f6ldqW7TmxV9SNWzZKSQ/view?us... ANd here lsblk as seen from 4.4.2 with an empty sda: https://drive.google.com/file/d/1wERp9HkFxbXVM7rH3aeIAT-IdEjseoA0/view?us... Here the command from 4.4.0 that shows no filter https://drive.google.com/file/d/1NKXAhkjh6bqHWaDZgtbfHQ23uqODWBrO/view?us... And here from 4.4.2 emergency mode, where I have to use the path /boot/ovirt-node-ng-4.4.2-0..../initramfs-.... because no initrd file in /boot (in screenshot you also see output of "ll /boot) https://drive.google.com/file/d/1ilZ-_GKBtkYjJX-nRTybYihL9uXBJ0da/view?us... I didn't anything special in 4.4.0: I installed node on the intended disk, that was seen as sdb and then through the single node hci wizard I configured the gluster volumes on sda Any suggestion on what to do on 4.4.2 initrd or running correct dracut command from 4.4.0 to correct initramfs of 4.4.2? BTW: could in the mean time if necessary also boot from 4.4.0 and let it go with engine in 4.4.2? Thanks, Gianluca