Red Hat Bugzilla – Bug 871083
Allow connection to the guest with non-responsive agent
Last modified: 2013-06-11 04:47:35 EDT
Description of problem:
Allow connection to the guest with non-responsive agent.
The current behaviour is a workaround for spicec limitation that when agent-related feature was requested from it, it stalled until it established communication with agent. Spice-gtk-based clients are more fault-tolerant in this respect so this hard limitation of User Portal could safely be turned to soft one ("Agent is not responsive. Some features may not work. [cancel] [connect anyway]").
Version-Release number of selected component (if applicable):
si19.1 / 3.1.0-18
Steps to Reproduce:
1. have a Windows VM with tools (mainly virtio-serial, rhev-agent and spice-vdagent running)
2. stop rhev-agent service
3. wait a while
4. try to connect to the VM again
you get this message:
Error while executing action VmLogon: Guest agent non-responsive
you get either dismissable warning (as outlined above; preferable solution) or no warning at all.
Created attachment 660798 [details]
warning dialog on spice connection to guest with non responsive agent
Simon - is the dialog in the attached picture seems ok? (if the user press cancel, the spice console connection is aborted, and if the user press ok the spice console is opened without logon)
Created attachment 661532 [details]
Updated screenshot for the proposed dialog
(In reply to comment #2)
> Simon - is the dialog in the attached picture seems ok? (if the user press
> cancel, the spice console connection is aborted, and if the user press ok
> the spice console is opened without logon)
What happens if the tools are not installed in the first place? does the pop-up shows or do we connect anyhow? If it is the same then please change the first line.
Could not connect to the agent on the guest, it may be unresponsive or not installed.
You can drop the third line, it's clear that the action is proceed or abort.
We also need the option ignore that message for good, but this is part of the persistent session issues or the VM configuration.
Created attachment 688902 [details]
engine log for period when guest agent was not running
OK, sf4. The popup appears in max time 125 seconds (120 time used by vdsm to trigger agent as non-responding, 5sec is HB time of agent). When agent is down, logging off and in in User Portal the popup is shows immediatelly, so OK.
I will discuss about this 125 seconds, if it could not be done shorter and based on this discussion there could be new BZ for improvement.
Ad 'do not show any more' checkbox, it does not exist now but if it would be implemented please reset this trigger when the VM is started again.
Proposed BZ905846 for cca 125 secs improvement.
3.2 has been released