Bug 1457970 - VMRC does NOT work if CFME is accessed with IPv6 Address
Summary: VMRC does NOT work if CFME is accessed with IPv6 Address
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.9.0
Assignee: Dávid Halász
QA Contact: Kedar Kulkarni
URL:
Whiteboard: ui:vmrc:console:ipv6
Depends On:
Blocks: 1464118
TreeView+ depends on / blocked
 
Reported: 2017-06-01 16:04 UTC by Kedar Kulkarni
Modified: 2018-03-06 14:42 UTC (History)
8 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1464118 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:42:43 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
VMRC Does not work with Server Name Could not be resolved (176.09 KB, image/png)
2017-06-01 16:04 UTC, Kedar Kulkarni
no flags Details

Description Kedar Kulkarni 2017-06-01 16:04:38 UTC
Created attachment 1284210 [details]
VMRC Does not work with Server Name Could not be resolved

Description of problem:
When CFME is accessed via IPv6 address instead of IPv4 or FQDN, it fails to connect to VMRC console.


Version-Release number of selected component (if applicable):
5.8.0.16

How reproducible:
Believe 100%

Steps to Reproduce:
1.Login to CFME with its IPv6 Address.
2.Add VMware as provider using its IPv6 Address. 
3.Find a running VM from Infrastructure-> Virtual Machines and open its details page. 
4. Click Access-> VM Console


Actual results:
See Screenshot attached.

Expected results:
VMRC Console should connect.

Additional info:
1. Tested this against Fedora and RHEL on Chrome and Firefox, all of those combinations did not work.
2. When tried to open VMRC console directly from vCenter web-client, I was able to open it with no issues.

Comment 13 Sudhir Mallamprabhakara 2017-06-21 14:49:24 UTC
Dávid Halász,

Spoke with KK about the bug. You are correct in saying that BZ description is a bit mis-leading. KK will look into updating that.

However, issue he reported was unable to access VMRC/HTML5 Remote console directly thru cfme appliance and not via vSphere web Client.

FYI: KK is able to access VMRC/HTML5 Remote console via vSphere web Client on vmrc-RHEL machine.

It took me couple of minutes to understand the issue. Maybe a blue jeans session would help.

@KK - Can you pls check with Dávid Halász's availability and setup a Blue Jeans session to explain?

Thanks
- Sudhir

Comment 14 Dávid Halász 2017-06-21 15:24:29 UTC
Sudhir,

I'm already delivering the fix for the issue so no further assistance is needed from my side.

Thanks

David

Comment 15 CFME Bot 2017-06-22 09:39:39 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:
https://github.com/ManageIQ/manageiq-ui-classic/commit/3e156df4111e1c324cf2d1c9c5710bdd6fad5263

commit 3e156df4111e1c324cf2d1c9c5710bdd6fad5263
Author:     Dávid Halász <dhalasz>
AuthorDate: Wed Jun 21 14:09:28 2017 +0200
Commit:     Dávid Halász <dhalasz>
CommitDate: Wed Jun 21 14:09:28 2017 +0200

    Prefer hostname over ip address when connecting to VMRC consoles
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1457970

 app/controllers/vm_remote.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comment 16 CFME Bot 2017-06-22 09:39:44 UTC
New commit detected on ManageIQ/manageiq-ui-classic/master:
https://github.com/ManageIQ/manageiq-ui-classic/commit/e2ddcb32fc332f452621000086626d46d0d71364

commit e2ddcb32fc332f452621000086626d46d0d71364
Author:     Dávid Halász <dhalasz>
AuthorDate: Wed Jun 21 14:09:57 2017 +0200
Commit:     Dávid Halász <dhalasz>
CommitDate: Thu Jun 22 10:47:33 2017 +0200

    Omit the brackets around IPv6 addresses when building URIs for VMRC
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1457970

 app/controllers/vm_remote.rb | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)


Note You need to log in before you can comment on or make changes to this bug.