Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 888774

Summary: [User Portal] UP->VM->Console: 'Remote Desktop' option - depends on guest agent (IP address)?
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: ovirt-engine-userportalAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Belka <jbelka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: dyasny, ecohen, iheim, michal.skrivanek, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: sf6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-11 09:15:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Belka 2012-12-19 13:10:31 UTC 
Description of problem:

User Portal->VM->Console: 'Remote Desktop' option should depend on guest agent running and providing guest's IP?

Version-Release number of selected component (if applicable):
si25.1

How reproducible:
100%

Steps to Reproduce:
1. A VM in UP without guest agent running
2. Change RDP
3. Open console
  
Actual results:

After opening console (and confirming popup dialog from Windows) nothing happens.

Expected results:

A error if an user changes console to RDP and UP doesn't know guest's IP from guest agent, or hide this feature if we know the VM doesn't have guest agent running.

Additional info:
Comment 1 Yaniv Kaul 2012-12-19 13:34:01 UTC 
No, it can use the VM's name - please test that if the VM name is its FQDN, or it has name+domain name (from the Windows domain name), it still works.
Comment 2 Jiri Belka 2012-12-19 14:19:42 UTC 
OK, if a VM name + domain is FQDN it works. But still, I think it would be wise to do a check to get IP (guest agent or dns) and if failed show a warning etc... Now opening console if IP info is unknown does nothing - no error, no warning.
Comment 3 Yaniv Kaul 2012-12-19 18:25:11 UTC 
(In reply to comment #2)
> OK, if a VM name + domain is FQDN it works. But still, I think it would be
> wise to do a check to get IP (guest agent or dns) and if failed show a
> warning etc... Now opening console if IP info is unknown does nothing - no
> error, no warning.

What I suspect is happening is that we don't catch RDP errors.
We used to.
Can you check what happens if the RDP is closed on the guest side?
See http://msdn.microsoft.com/en-us/library/windows/desktop/aa382170(v=vs.85).aspx (bottom especially)
Comment 7 Tomas Jelinek 2013-01-15 07:57:32 UTC 
After a quick look at the code we indeed don't catch the RDP errors. 

The situation is even more strange with SPICE, where we catch the errors, and than throw a NotImplementedException().
Comment 8 Tomas Jelinek 2013-01-16 07:04:28 UTC 
http://gerrit.ovirt.org/#/c/11052/
Comment 9 Tomas Jelinek 2013-01-21 09:32:27 UTC 
merged U/S: 42894d12a1bc182263359da93e12b2dfd29afdbb
Comment 12 Jiri Belka 2013-02-13 08:51:23 UTC 
ok, sf6.
Comment 13 Itamar Heim 2013-06-11 09:15:23 UTC 
3.2 has been released
Comment 14 Itamar Heim 2013-06-11 09:40:48 UTC 
3.2 has been released