When working with telemetry-framework, we found that the GlusterFS system would fail on host OS reboot even after starting the virtual machines back up. The reason is that /dev/vdb doesn't seem to get reattached on reboot.
We should validate that is still the case after https://github.com/redhat-nfvpe/base-infra-bootstrap/issues/50 is resolved, and if so, figure out how to modify spinup.sh template to have virt-install set the second disk to be attached automatically at boot.
Alternatively, this could be an /etc/fstab problem in the virtual machine as well, where the second disk isn't setup to automount on boot.
When working with telemetry-framework, we found that the GlusterFS system would fail on host OS reboot even after starting the virtual machines back up. The reason is that
/dev/vdb
doesn't seem to get reattached on reboot.We should validate that is still the case after https://github.com/redhat-nfvpe/base-infra-bootstrap/issues/50 is resolved, and if so, figure out how to modify
spinup.sh
template to havevirt-install
set the second disk to be attached automatically at boot.Alternatively, this could be an
/etc/fstab
problem in the virtual machine as well, where the second disk isn't setup to automount on boot.