Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 905846

Summary:	[RFE] [User Portal] SPICE features degration popup, solve cca 125 secs delay
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Jiri Belka <jbelka>
Component:	ovirt-engine-userportal	Assignee:	Michal Skrivanek <michal.skrivanek>
Status:	CLOSED WONTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, djasa, dyasny, ecohen, iheim, michal.skrivanek, Rhev-m-bugs, ykaul
Target Milestone:	---	Keywords:	Improvement
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-08 09:25:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Belka 2013-01-30 10:04:16 UTC

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):
sf4

How reproducible:
100%

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:
https://bugzilla.redhat.com/show_bug.cgi?id=871083
and especially https://bugzilla.redhat.com/show_bug.cgi?id=871083#c16

Comment 1 Jiri Belka 2013-01-30 10:07:47 UTC

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 10:55:18 UTC

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 09:25:34 UTC

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