Bug 1638217 - VM portal always asks how to open console.vv even it has been set to default application.
Summary: VM portal always asks how to open console.vv even it has been set to default ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-web-ui
Version: 4.2.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.4.2
: ---
Assignee: Hilda Stastna
QA Contact: Ivana Saranova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-11 06:37 UTC by Kumar Mashalkar
Modified: 2023-12-15 16:11 UTC (History)
10 users (show)

Fixed In Version: ovirt-web-ui-1.6.4-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-23 16:11:04 UTC
oVirt Team: UX
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-web-ui pull 1243 0 None closed Allow opening console.vv in virt-viewer when clicking on VM console in Firefox 2021-01-07 12:00:59 UTC
Red Hat Issue Tracker RHV-37233 0 None None None 2022-07-09 13:04:06 UTC
Red Hat Knowledge Base (Solution) 3674521 0 None None None 2020-01-28 10:31:46 UTC
Red Hat Product Errata RHSA-2020:3807 0 None None None 2020-09-23 16:11:39 UTC

Description Kumar Mashalkar 2018-10-11 06:37:41 UTC
Description of problem:

When user selects virt-viewer as default application in Firefox, It still prompts for how to open the file.

This happens only when VM portal is used and does not happen with Admin portal.

Version-Release number of selected component (if applicable):
RHV 4.2 VM portal

How reproducible:
100%

Steps to Reproduce:
1. Open Firefox settings and set virt-viewer as default application to open .vv file.
2. Open RHV-Manager VM portal and click on VM console.
3. It prompts for application to use for console.

Actual results:
It prompts window to open console.vv while using VM portal.

Expected results:
Directly Virt-Viewer/Remote-viewer application should open with VM console.

Additional info:
1) I have observed that the "from" part of the prompt is RHV-M FQDN when opened from Admin portal. Where as for VM portal the prompt is having "from" part as "data:" <blank>

2) Also, When I edited the console.vv from Admin portal and VM portal there is difference in URL used.

I will attach the prompt window in the case for further understanding.

Comment 2 Greg Sheremeta 2018-10-11 14:35:30 UTC
I duplicated. It only happens on Firefox -- chrome is fine.

In admin portal, it's a regular request (cause = 'subdocument' in network tab) for the .vv file. In vm portal, it's an xhr (cause = 'xhr') request. Firefox must not handle that the same.

Comment 3 Michal Skrivanek 2018-10-12 06:32:03 UTC
which Firefox is that exactly?

Comment 5 Sandro Bonazzola 2019-01-28 09:40:52 UTC
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 7 Daniel Gur 2019-08-28 13:14:16 UTC
sync2jira

Comment 8 Daniel Gur 2019-08-28 13:19:18 UTC
sync2jira

Comment 14 Scott Dickerson 2020-06-17 23:52:21 UTC
I looked into this a bit awhile ago, here are my thoughts on doing the console.vv on server side:

  - The console.vv isn't just passed along from the API, it goes through an adjustment.
    The function is in [0].

  - Whatever is done in that function needs to be duplicated on the server code, or it needs
    to be dropped.

  - I don't know why the console.vv is adjusted like this, except maybe to adopt some
    configurations that are stored on web-ui itself.

  - Webadmin will also generate a console.vv file, but the GWT code does stuff and then routes
    the browser along to "/ovirt-engine/services/attachment/console.vv" which is [1].  Looks
    like that servlet just takes POST data and returns it as the response.  The bit of GWT code
    that actually calls it is [2].


Given all of that info, there are a few things that we could do:

  - Reimplement the GetAttachmentServlet in ovirt-web-ui modeled after the branding jsp [3]

  - Maybe reuse the one in webadmin.  It'll probably work as long as the SSO tokens get
    passed along, the URL is formed correctly and web-ui is running in the engine.  Just
    need to get the POST request fired in the right way.  GWT code inserts a form, submits
    it and targets the response to open in an iframe (if I saw things happen correctly).

  - If we want it to work when web-ui is running in dev mode (like how the container does
    it), something will probably have to be done in the webpack dev server proxy configs
    to enable access to something other than the rest endpoints.  Maybe it can be configured
    with another proxy for the GetAttachementServlet when running in dev mode.
    Prod/installed mode would use the jsp or engine's attachment servlet.


[0] - https://github.com/oVirt/ovirt-web-ui/blob/master/src/sagas/console/vvFileUtils.js

[1] - https://github.com/oVirt/ovirt-engine/blob/master/backend/manager/modules/services/src/main/java/org/ovirt/engine/core/services/GetAttachmentServlet.java

[2] - https://github.com/oVirt/ovirt-engine/blob/2b34f2d3b8fa2aea63883e59418148598c4eb05f/frontend/webadmin/modules/uicommonweb/src/main/java/org/ovirt/engine/ui/uicommonweb/models/vms/ConsoleModel.java#L205-L224

[3] - https://github.com/oVirt/ovirt-web-ui/blob/master/packaging/ovirt-web-ui.war/WEB-INF/branding.jsp

Comment 15 Hilda Stastna 2020-07-02 16:49:41 UTC
Fix: https://github.com/oVirt/ovirt-web-ui/pull/1243

Comment 18 Ivana Saranova 2020-08-20 23:53:57 UTC
Steps:
1. Open Firefox settings and set virt-viewer as default application to open .vv file.
2. Open RHV-Manager VM portal and click on VM console.
3. It prompts for application to use for console.

Results:
Download window is only shown when no default behavior is set in the browser. After changing the settings, virt-viewer is used directly skipping the download prompt window.

Verified in:
ovirt-engine-4.4.2.3-0.6.el8ev.noarch
ovirt-web-ui-1.6.4-1.el8ev.noarch
firefox-78.0.2-1.fc31.x86_64

Comment 21 Sharon Gratch 2020-09-01 17:26:31 UTC
Created attachment 1713354 [details]
downloaded console file name

Comment 28 errata-xmlrpc 2020-09-23 16:11:04 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 (Moderate: Red Hat Virtualization security, bug fix, and enhancement update), 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-2020:3807


Note You need to log in before you can comment on or make changes to this bug.