Created attachment 733546[details]
engine.log and vdsm.log
Description of problem:
BZ871083 introduced a feature which informs a user that SPICE would not have all features if there's problem to communicate with guest agent. This works for Windows guest but I see it is not working with a Linux guest.
I don't see in engine.log any VmLogonVDS method called for Linux guest.
This is for Windows VM with stopped agent.
2013-04-10 10:04:16,988 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp-/127.0.0.1:8702-13) [64b56479] Running command: SetVmTicketCommand internal: false. Entities affected : ID: 0dd9fc10-9d5a-4cab-9a89-8abf564c32e0 Type: VM
2013-04-10 10:04:17,050 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp-/127.0.0.1:8702-13) [64b56479] START, SetVmTicketVDSCommand(HostName = dell-r210ii-03, HostId = 571f2135-3b5f-4f8e-b085-b2bf3a7bd6df, vmId=0dd9fc10-9d5a-4cab-9a89-8abf564c32e0, ticket=cOX/h1og8ZM/, validTime=120,m userName=portaluser2, userId=77e2e25b-4eb5-4f87-9031-34950190e8b3), log id: 558881f0
2013-04-10 10:04:17,150 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp-/127.0.0.1:8702-13) [64b56479] FINISH, SetVmTicketVDSCommand, log id: 558881f0
2013-04-10 10:04:17,189 WARN [org.ovirt.engine.core.dal.job.ExecutionMessageDirector] (ajp-/127.0.0.1:8702-5) [3af46950] The message key VmLogon is missing from bundles/ExecutionMessages
2013-04-10 10:04:17,213 INFO [org.ovirt.engine.core.bll.VmLogonCommand] (ajp-/127.0.0.1:8702-5) [3af46950] Running command: VmLogonCommand internal: false. Entities affected : ID: 0dd9fc10-9d5a-4cab-9a89-8abf564c32e0 Type: VM
2013-04-10 10:04:17,274 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmLogonVDSCommand] (ajp-/127.0.0.1:8702-5) [3af46950] START, VmLogonVDSCommand(HostName = dell-r210ii-03, HostId = 571f2135-3b5f-4f8e-b085-b2bf3a7bd6df, vmId=0dd9fc10-9d5a-4cab-9a89-8abf564c32e0, domain=rhev.lab.eng.brq.redhat.com, password=******, userName=portaluser2), log id: 6fa34cfd
2013-04-10 10:04:17,298 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (ajp-/127.0.0.1:8702-5) [3af46950] Failed in VmLogonVDS method
2013-04-10 10:04:17,299 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (ajp-/127.0.0.1:8702-5) [3af46950] Error code nonresp and error message VDSGenericException: VDSErrorException: Failed to VmLogonVDS, error = Guest agent non-responsive
For Linux guest with stopped agent:
2013-04-10 10:09:26,574 INFO [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp-/127.0.0.1:8702-9) [3fb4ee5] Running command: SetVmTicketCommand internal: false. Entities affected : ID: de62abf4-d9e7-471f-b892-62d0f9bcf95f Type: VM
2013-04-10 10:09:26,638 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp-/127.0.0.1:8702-9) [3fb4ee5] START, SetVmTicketVDSCommand(HostName = dell-r210ii-03, HostId = 571f2135-3b5f-4f8e-b085-b2bf3a7bd6df, vmId=de62abf4-d9e7-471f-b892-62d0f9bcf95f, ticket=I+7VdtfP5Plm, validTime=120,m userName=portaluser2, userId=77e2e25b-4eb5-4f87-9031-34950190e8b3), log id: 83f7092
2013-04-10 10:09:26,722 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp-/127.0.0.1:8702-9) [3fb4ee5] FINISH, SetVmTicketVDSCommand, log id: 83f7092
So it seems there's no check for guest agent when it is Linux guest. VmLogonVDS method does not appear even when Linux guest agent is running.
Version-Release number of selected component (if applicable):
sf13
How reproducible:
100%
Steps to Reproduce:
1. have a Windows VM with guest agent
2. open spice console for Windows guest
3. stop Windows guest agent
4. wait 125 seconds
5. open spice console for Windows guest
6. have a Linux VM with guest agent
7. open spice console for Linux guest
8. stop Linux guest agent
9. wait 125 seconds
10. open spice consoel for Linux guest
Actual results:
2 - no popup
5 - Guest Agent is not respoding popup
7 - no popup
10 - no popup
Expected results:
step 10 should probably behave like step 5, thus showing Guest Agent is not respoding popup
Additional info:
applies both to admin portal and user portal
times in logs
10:02 stopping windows agent
10:04 windows console with stopped agent
10:06 linux console with agent running
10:09 linux console with stopped agent
It should be solved by the fix for BZ922398:
currently the guest agent names on operating systems different than windows is different than what the engine looks for, so it concludes that the guest agent doesn't exist and it won't even try to sign on to the guest (and the expected popup is shown in case the SSO fails).