Created attachment 1681158 [details]
Description of problem:
When a user creates and starts up a Windows VM, after a while of running the VM has Status Stopping.
VM Events gives an error about Readiness probe:
Readiness probe errored: rpc error: code = Unknown desc = container is not created or running
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a Windows VM, start it, wait
VM is in Stopping status
Assigning to Filip after offline discussion
This bug was discovered due to another bug where a running virt-launcher crashed, which incorrectly caused the VM to report status Stopping instead of Pod Error.
Since I'm not able to reproduce this, I can't verify the VM Status transition Running -> Pod Error.
I have verified that VM Status reports correctly for regular situations and with a virt-launcher pod in Error state.
Verified with release-4.5 commit: 91e682e014286e243085dcb168480d54b913a010
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.