Previously, when executing the "service virt-who restart" command on a virtual machine via the secure shell (SSH) network protocol, the security lock prevented the service from reconnecting after the restart. Therefore, when running two virtual machines simultaneously, restarting the first machine reported the following message in the output of the "virt-who service status" command executed on the second machine:
virt-who dead but pid file exists
The bug has been fixed, and the virt-who agent now handles the aforementioned situation properly.
Prior to this update, the virt-who agent failed to monitor the guest start event after performing a specific set of user operations. Consequently, the virt.uuid of the guest could not be reported. The bug has been fixed, and the virt.uuid identifications are now provided correctly regardless of previous operations.
Previously, when starting the virt-who service with the "virt-who -d" command, the background loop was created, even though the virt-who agent was not in the background mode. With this update, the background loop is no longer accidentally initiated in the described scenario.
Previously, when the virt-who agent was started as a service in the background, the debug log appeared in the shell prompt. This behavior has been corrected, and the debug log is no longer displayed in the aforementioned case.
In the virt-who configuration file, setting the "VIRTWHO_INTERVAL" option to any number enables sending a list of virtual guests to a log file automatically at the given time interval. Due to a bug, this functionality was blocked, therefore the log file was not updated as expected. The bug has been fixed, and now the log file is updated as frequently as set in the "VIRTWHO_INTERVAL" option.
Previously, when the virt-who agent was running in debug mode, it failed to create or recover a connection to a virtual machine. Consequently, the following message was displayed:
ERROR: Unable to create connection
With this update, the bug has been fixed and the virt-who agent properly connects with the debug mode enabled.
Previously, when running the virt-who service in vdsm mode, unregistering the system from the SAM (Red Hat Subscription Asset Manager) server caused the service to crash with the following message:
virt-who dead but subsys locked
This bug has been fixed and virt-who now works properly in the described case.
Previously, when running the "service virt-who restart" command repeatedly in very short time intervals, the command failed to stop the virt-who process, but started a new process successfully. Consequently, many virt-who processes could have ended up running simultaneously. This bug has been fixed, and running "service virt-who restart" repeatedly no longer results in multiple processes being started.