Bug 905846 - [RFE] [User Portal] SPICE features degration popup, solve cca 125 secs delay
[RFE] [User Portal] SPICE features degration popup, solve cca 125 secs delay
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-userportal (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Michal Skrivanek
Pavel Stehlik
: Improvement
Depends On:
  Show dependency treegraph
Reported: 2013-01-30 05:04 EST by Jiri Belka
Modified: 2013-03-08 04:25 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-03-08 04:25:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jiri Belka 2013-01-30 05:04:16 EST
Description of problem:

SF4 introduced a popup which informs a user in User Portal about SPICE features degradation when guest agent is not running (basically guest agent is here to check is SPICE agents are available). Problem is that User Portal works with vdsm which triggers guest agent nonresponding after 120 secs, plus we could take in account 5 secs for guest agent's heartbeat interval.

This make appearing popup after cca 125 secs, before this time period the popup doesn't appear. Thus the SPICE degradation warning is not applied in this "125secs" period where guest agent is not available as well.

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

How reproducible:

Steps to Reproduce:
1. install guest tools
2. stop guest agent
3. open immediatelly spice console
Actual results:
non popup

Expected results:
popup should appear always when agent is not available, some realtime check before each spice console opening?

Additional info:
and especially https://bugzilla.redhat.com/show_bug.cgi?id=871083#c16
Comment 1 Jiri Belka 2013-01-30 05:07:47 EST
David (djasa), as you are original BZ reporter, do you agree and/or have any comments about this?
Comment 2 David Jaša 2013-01-30 05:55:18 EST
Makes sense IMO.

In addition, no popup could be given when the rhev-agent (tools) isn't installed at all.
Comment 3 Michal Skrivanek 2013-03-08 04:25:34 EST
this was the initial decision to use 120s time period before considering agent not working. 
We do want to overhaul the locking in 3.3+ and change the reporting/locking mechanism anyway so this one is IMHO not worth addressing

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