Bug 1500995

Summary:	Unable to initiate VM console in VMware environment with 6.5 VC and ESXi 6.5
Product:	Red Hat CloudForms Management Engine	Reporter:	Ryan Spagnola <rspagnol>
Component:	UI - OPS	Assignee:	Brian McLaughlin <bmclaugh>
Status:	CLOSED ERRATA	QA Contact:	Kedar Kulkarni <kkulkarn>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.7.0	CC:	abellott, bmclaugh, cpelland, dclarizi, dhalasz, hkataria, jhardy, kkulkarn, mfeifer, mpovolny, obarenbo, rspagnol, simaishi, smallamp
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.4
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	5.7.4.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-18 20:30:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	Bug
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:
Embargoed:

Description Ryan Spagnola 2017-10-12 00:16:07 UTC

Description of problem:
We currently have console working in production running vCenter 6.5 with Hypervisors running 5.5 and once the Hypervisors are upgrade to 6.5 the console no long works.

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

How reproducible:
Always

Steps to Reproduce:
1. create environment with CFME at 5.7.3.2 with VC 6.5 and ESXi 6.5 with VMs discovered into the VMDB. Use CFME to attempt to initiate VM console.
2.
3.

Actual results:


Expected results:


Additional info:
Appache crashing after applying the 5.7.3.2-9 hotfix
https://bugzilla.redhat.com/show_bug.cgi?id=1468633

Comment 2 Brian McLaughlin 2017-10-12 15:47:20 UTC

Are you able to provide logs (production log, web browser javascript console errors) when the error occurs?  Also, which VMware console type (under Configuration - VMware Console Support).

Comment 4 CFME Bot 2017-10-20 14:01:40 UTC

https://github.com/ManageIQ/manageiq/pull/16247

Comment 5 Dave Johnson 2017-11-03 21:06:37 UTC

KK, is this the same issue we have been chasing and is ultimately resolved with the same PRs if they are backported?

Comment 6 Kedar Kulkarni 2017-11-03 23:13:37 UTC

Hey Dave, this is slightly different issue. It seems to be with OPS UI, the button might not be correctly disabled. PR in comment 4 should address that issue.

Comment 7 CFME Bot 2017-11-06 18:21:04 UTC

New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/29c21e060e4f64502545d3136ba75b6f82a497b7

commit 29c21e060e4f64502545d3136ba75b6f82a497b7
Author:     Brian McLaughlin <bmclaugh>
AuthorDate: Thu Oct 19 16:28:21 2017 -0400
Commit:     Brian McLaughlin <bmclaugh>
CommitDate: Thu Oct 19 16:28:21 2017 -0400

    Disable VNC console button when VMware api is > 6
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1500995

 app/helpers/application_helper/toolbar_builder.rb       |  4 ++++
 spec/helpers/application_helper/toolbar_builder_spec.rb | 15 +++++++++++++++
 2 files changed, 19 insertions(+)

Comment 9 Kedar Kulkarni 2017-11-27 17:51:02 UTC

On 5.7.4.1, OPS UI,
for VMware 6.0 - VM Console was Accessible 
for VMware 6.5 - VM Console was Disabled correctly.

Comment 12 errata-xmlrpc 2017-12-18 20:30:46 UTC

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.

https://access.redhat.com/errata/RHSA-2017:3484