Unable to Open VNC Console: "Malformed request URL (400)

Problem

• The VNC console is unable to be viewed for an instance via the Clarity UI under the "Instances" tab.

Screen_Shot_2018-10-16_at_12.58.50_PM.png

• The following message is displayed on the page.

None

{"badRequest": {"message": "Malformed request URL: URL's project_id 'XXXXXX' doesn't match Context's project_id 'XXXXX'", "code": 400}}

Environment

• Platform9 Managed OpenStack - v3.5.0-3.5.6

• Nova

• NoVNC

Cause

An incorrectly scoped X-Auth-Token is used if you try to access an instance's VNC console for an instance that does not belong to the tenant to which you are currently logged in. This may also happen after switching tenants.

Resolution

If you are using a Platform9 Managed OpenStack release version lower than 3.5.7, and you encounter this issue as a result of switching tenants, use the steps given below to resolve the issue.

1. Navigate to the Instances tab in the Platform9 Clarity UI.

2. Refresh the page.

3. Click Console for the instance once again

4. The VNC console should load successfully.

Note: An instance's VNC console URL may also be obtained via the OpenStack CLI. Refer to: OpenStack Docs - Access an instance through a console