Cannot Access VM Console for VMware provider

[SanthoshRam-03]

In the ManageIQ production environment, attempting to access the VM console results in an error where the WebMKS connection gets stuck at "WEBMKS Connecting.".

Steps to reproduce:

1. Navigate to Compute -> Infrastructure -> Virtual Machines -> VMs & Templates.
2. Select the desired VM.
3. Click on the "Access" dropdown and choose "VM Console.".
4. The WebMKS connection interface appears and remains stuck at "WEBMKS Connecting.".

Expected Behavior:
The VM console should successfully connect to and display the VM interface.

Observed Behavior:
The WebMKS interface is stuck at "WEBMKS Connecting" and does not proceed to display the VM console.

Environment Details:

ManageIQ version: Petrosian
Provider: VMware
VM state: Powered On

[SanthoshRam-03]

Hi @Fryguy, any updates regarding this issue?

[Fryguy]

@GilbertCherrie Can you take a look at this one? I know we fixed something regrading vm consoles, but I can't remember if it landed in Petrosian or not.

[GilbertCherrie]

I tried to replicate this locally but I can't get the console page to load probably due to lacking a real provider. However, given this issue: #22954 it seems the page is functional and other users are able to connect to the console.

@Fryguy The issue that was fixed was a sizing issue fixed by this pr: ManageIQ/manageiq-ui-classic#8919 and backported to Morphy, Petrosian and Quinteros.

[SanthoshRam-03]

Hi @GilbertCherrie @Fryguy,

As per the redhat kcs, we have extracted the webmks in the /var/www/miq/public path. after that, we trying to connect the vmware console. but it seems to be connecting

https://access.redhat.com/solutions/3376081

we followed the above doc.

[GilbertCherrie]

Sounds good, can we close out this issue then?

[remo233]

Hi @GilbertCherrie ,

Actually what santhosh trying to say is, he have configured the webmks package in manageiq like mentioned in the redhat kcs. But however, it is not working for him.

[GilbertCherrie]

Do you have any logs with errors available that we can read through?

[SanthoshRam-03]

Hi @GilbertCherrie Here are the VMConsole related logs for your reference.

[GilbertCherrie]

@Fryguy I don't think this is a UI issue. There is probably something wrong with the configuration which is causing it to fail to connect. I can't recreate this since I don't have any real provider data to test with but looking at this issue: #22954 it looks like the Webmks console loads properly in the UI.

[Fryguy]

I wonder of something changed with WebMks itself or perhaps VMware. cc @agrare

[agrare]

@SanthoshRam-03 @remo233 what version of vSphere and what version of the HTML Console SDK are you using?

[agrare]

@GilbertCherrie have you tested this lately?

Not sure if it is related but when I tried this out I get the following error in my rails server

[----] I, [2024-07-17T12:02:22.626893#107775:f348]  INFO -- : Started GET "/ws/console/61aa428ffd5b940ab2e18325d779f60e" for 127.0.0.1 at 2024-07-17 12:02:22 -0400
[----] F, [2024-07-17T12:02:22.677359#107775:f348] FATAL -- :   
ActionController::RoutingError (No route matches [GET] "/ws/console/61aa428ffd5b940ab2e18325d779f60e"):
  

[GilbertCherrie]

@agrare No I don't have any actual provider to test this with. I just saw a similar issue opened around the same time as this where they were able to access the console but it was just not scaling properly in the browser

[agrare]

@GilbertCherrie well that is easy to fix :D I sent you one

[agrare]

I just tested this on an appliance and a vSphere version 7.0.3.01700 and it works fine.

[remo233]

Adam, glad to hear from you. Could you please share the steps to resolve this ?

…

On Wed, Jul 17, 2024, 10:44 PM Adam Grare ***@***.***> wrote: I just tested this on an appliance and a vSphere version 7.0.3.01700 and it works fine. — Reply to this email directly, view it on GitHub <#23053 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZO3IVUIPACJ6WFXXAMMRWLZM2RALAVCNFSM6AAAAABISRRYOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZTHAYDEOBYGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[agrare]

@remo233 I didn't do anything to fix it, it was working normally. The routing error was only when running in development mode, I assume you're using an appliance or podified @remo233 ? Can you please post your vsphere and html console sdk versions?

[miq-bot]

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.