Il giorno ven 23 ago 2019 alle ore 11:27 Gianluca Cecchi < gianluca.cecchi(a)gmail.com&gt; ha scritto: No, doesn't make sense. nodectl checks for oVirt Node specific configuration. # nodectl check Status: OK Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... OK Checking available space in thinpool ... OK Checking thinpool auto-extend ... OK vdsmd ... OK # nodectl info layers: ovirt-node-ng-4.3.2-0.20190313.0: ovirt-node-ng-4.3.2-0.20190313.0+1 bootloader: default: ovirt-node-ng-4.3.2-0.20190313.0+1 entries: ovirt-node-ng-4.3.2-0.20190313.0+1: index: 0 title: ovirt-node-ng-4.3.2-0.20190313.0 kernel: /boot/ovirt-node-ng-4.3.2-0.20190313.0+1/vmlinuz-3.10.0-957.5.1.el7.x86_64 args: "ro crashkernel=auto rd.lvm.lv=onn_host/swap rd.lvm.lv=onn_host/ovirt-node-ng-4.3.2-0.20190313.0+1 rhgb quiet LANG=en_US.UTF-8 img.bootid=ovirt-node-ng-4.3.2-0.20190313.0+1" initrd: /boot/ovirt-node-ng-4.3.2-0.20190313.0+1/initramfs-3.10.0-957.5.1.el7.x86_64.img root: /dev/onn_host/ovirt-node-ng-4.3.2-0.20190313.0+1 current_layer: ovirt-node-ng-4.3.2-0.20190313.0+1 what's the use case here? check host sanity? because nodectl is not checking that, it just check node config matches to requirements to be able to perform rollback if needed. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*