Red Hat Bugzilla – Bug 1500995
Unable to initiate VM console in VMware environment with 6.5 VC and ESXi 6.5
Last modified: 2017-12-18 15:30:46 EST
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
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).
https://github.com/ManageIQ/manageiq/pull/16247
KK, is this the same issue we have been chasing and is ultimately resolved with the same PRs if they are backported?
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.
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/29c21e060e4f64502545d3136ba75b6f82a497b7 commit 29c21e060e4f64502545d3136ba75b6f82a497b7 Author: Brian McLaughlin <bmclaugh@redhat.com> AuthorDate: Thu Oct 19 16:28:21 2017 -0400 Commit: Brian McLaughlin <bmclaugh@redhat.com> 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(+)
On 5.7.4.1, OPS UI, for VMware 6.0 - VM Console was Accessible for VMware 6.5 - VM Console was Disabled correctly.
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