Description of problem: When opening a web console to a VM via WebMKS the connection hangs on some VMs. This occurs on some VMs and not others on the same hypervisor. - We have compared VMware hardware versions and settings and cannot find a common denominator. - We have removed a VM from CFME and allowed it to be rediscovered with no change. - We have verified the consoles work with both VMware vCenter and ManageIQ for the same VMs. The connection from CFME loads the new browser tab and list WebMKS and Connecting in the lower left corner but fail to ever make the connection. Version-Release number of selected component (if applicable): 5.8.2.3 vSphere 6.5 with multiple versions of ESXi including 6 and 6.5 How reproducible: Varies Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: * tested with Firefox on a RHEL workstation and Chrome/Safari from Mac OSX * customer has already installed the hotfix from https://bugzilla.redhat.com/show_bug.cgi?id=1523404 and has informed that the symptoms are different now.
By using the solution from following article: https://communities.vmware.com/thread/546184 I was able to get the WebMKS Console for the VMs which had issues (keep saying connecting indefinitely) were resolved. To access the vmx file, you can ssh to ESXi host and do: vi /vmfs/volumes/datastore/virtual_machine_directory/virtual_machine_name.vmx and change the RemoteDisplay.vnc.enabled = "true" to RemoteDisplay.vnc.enabled = "false" and save the file. Note that VM needs to be powered off before you can edit the file. Thereafter WebMKS and HTML5 console should work.
https://github.com/ManageIQ/manageiq-providers-vmware/pull/220
Hey, Brian. This is a blocker for this release. Build next week. What's up?
Well, I've successfully reconfigured a VM for WebMKS when attempting a WebMKS console connection to it. Unfortunately, thus far those changes only take effect after restarting the VM. Research is continuing.
Comment 3 above describes the current steps to configure individual VMs for WebMKS console access. That along with our current documentation on configuring our appliances for WebMKS consoles [1] should resolve the connection issues noted in the BZ description. I'm currently researching/working on a way to automate that configuration when connecting to a WebMKS console (seems like an RFE), but am not confident it is possible without requiring the VM to be rebooted. [1] https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/managing_infrastructure_and_inventory/sect_virtual_machines#configuring-the-webmks-support