The libvirt driver knows only a single method for reboot. The input parameter reboot_type specifies if soft or hard reboot should be made.
In the libvirt case they also do a hard reboot if a soft reboot fails. So triggering soft-reboot might result in a hard reboot... As we're not supporting a soft reboot, we directly do the hard reboot - ok.
Maybe it makes sense to at least add a log.warning statement that a hard reboot was made although a soft reboot was requested?
The libvirt driver knows only a single method for reboot. The input parameter reboot_type specifies if soft or hard reboot should be made.
In the libvirt case they also do a hard reboot if a soft reboot fails. So triggering soft-reboot might result in a hard reboot... As we're not supporting a soft reboot, we directly do the hard reboot - ok.
Maybe it makes sense to at least add a log.warning statement that a hard reboot was made although a soft reboot was requested?