Bug 1073440

Summary:	spice console icon is active, even though there is already an open console
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ilanit Stein <istein>
Component:	ovirt-engine-webadmin-portal	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	acathrow, ecohen, gklein, iheim, michal.skrivanek, Rhev-m-bugs, sherold, yeylon
Target Milestone:	---	Keywords:	Regression, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-25 12:48:54 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 Ilanit Stein 2014-03-06 12:57:29 UTC

Description of problem:
In av2, after open a VM spice console, it is possible to open another one.

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

How reproducible:
100%

Expected results:
Console icon should be blocked after opening one console.

Additional info:
This second open allowed, crashes the spice plugin.
bug is will be added soon.

Comment 1 Ilanit Stein 2014-03-06 13:38:07 UTC

bug that crashes spice plug in: bug 1073461

Comment 2 Michal Skrivanek 2014-03-09 12:15:51 UTC

we don't really want to block it anymore, for .vv launch we can't even enforce such a thing. I'm proposing WONTFIX

Comment 3 Scott Herold 2014-03-10 12:51:41 UTC

Michal,

Is there a situation in 3.4 that an or would allow more than one active console as to why we don't want to fix this?  Crashing the spice client is not the desired behavior.

Comment 4 Scott Herold 2014-03-25 12:48:54 UTC

We don't consider this a bug.  We will continue to track BZ 1073461 for spice crash.

Comment 5 Ilanit Stein 2014-03-25 13:43:43 UTC

In case the spice console icon will remain active, after a console is already opened, pressing it again, the expected behaviour should be to close the connection and open a new one.

Comment 6 Michal Skrivanek 2014-10-31 11:03:22 UTC

(In reply to Scott Herold from comment #3)
> Michal,
> 
> Is there a situation in 3.4 that an or would allow more than one active
> console as to why we don't want to fix this?  Crashing the spice client is
> not the desired behavior.

we don't allow more consoles (though have an RFE for it)
the original (standalone) client gets closed (might be ungracefully)
the browser js clients..well. probably just get a disconnect, don't know