Bug 1395786 - html5 spice client fails to show a human-readable representation of Event object
Summary: html5 spice client fails to show a human-readable representation of Event object
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Tomas Jelinek
QA Contact: Angelina Vasileva
URL:
Whiteboard: ui:html5
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-16 16:23 UTC by movciari
Modified: 2019-05-20 14:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-02 14:30:23 UTC
Category: Bug
Cloudforms Team: RHEVM
Target Upstream Version:


Attachments (Terms of Use)

Description movciari 2016-11-16 16:23:10 UTC
Description of problem:
When connection to spice console of VM in RHV fails, browser shows:
[object Event]
It should show a human-readable representation of Event object, or even better, some information about error that happened.

Version-Release number of selected component (if applicable):
5.7.0.10

How reproducible:
always

Steps to Reproduce:
1. get CFME version affected by https://bugzilla.redhat.com/show_bug.cgi?id=1395782 or https://bugzilla.redhat.com/show_bug.cgi?id=1393520
2. follow reproduction steps for one of the mentioned bugs (steps copied below to reproduce this bug:

3. Manage RHEVM provider (say RHEVM 36 or 35)
4. Navigate to Compute ==> Infrastructure ==> Virtual Machines ==> Select a Virtual Machine
5. Click on the HTML5 icon in the vm details page

Actual results:
you can see [object Event]

Expected results:
Error, or at least human-readable representation of Event object

Additional info:

Comment 2 Oved Ourfali 2016-11-17 06:17:21 UTC
Toman - can you take a look?

Comment 3 Tomas Jelinek 2016-11-18 11:29:53 UTC
This is actually an issue in the SPICE-HTML5 itself. 

It has been enhanced a bit by:
https://github.com/SPICE/spice-html5/commit/b926f062f35e298f65828d9835f5b35895ec3729

which means that the javascript console will contain something like:
ERROR: WebSocket error: Can't connect to websocket on URL: ws://192.168.122.137:3000/ws/console/86e96b1eb158eb80d3ab41926a7c620d

Im not sure we want to invest time in further enhancing it.
Oved?

Comment 4 Oved Ourfali 2016-11-18 12:03:45 UTC
Was their fix already released? 
Assuming they have a fix, do we need to do anything special in order to show then error instead of the object?

Comment 5 Tomas Jelinek 2016-11-18 12:36:22 UTC
That has already been released and used in current cfme. The thing is that the screen indeed contains the "[object Event]". The fix I've referenced only adds also a console.log() to javascript console with the message "ERROR: WebSocket error: Can't connect to websocket on URL: ...". In order to see it you need to press ctrl+shift+j or similar.

So, the question is if we want to contribute to the spice-html5 something which would do some more sophisticated error reporting also on screen or we want to open a bug against it.

But one way or the other, I don't think this is a CFME z-stream material, it does not block the user from anything, just the error message is not informative.

Comment 6 Oved Ourfali 2016-11-18 13:09:49 UTC
Okay. 
Please file a bug on spice, and I've pushed this one to future.

Comment 7 Dave Johnson 2017-07-14 03:49:13 UTC
Please assess the importance of this issue and update the priority accordingly.  Somewhere it was missed in the bug triage process.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 8 Josh Carter 2018-10-02 14:30:23 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 9 Josh Carter 2018-10-02 14:32:53 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


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