Bug 803345

Summary:	vncviewer pkg should be installed automatically when installing oVirt CLI
Product:	[Retired] oVirt	Reporter:	Avihai Shoham <ashoham>
Component:	ovirt-engine-cli	Assignee:	Michael Pasternak <mpastern>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	acathrow, bazulay, iheim, oschreib, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-15 15:36:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Avihai Shoham 2012-03-14 13:49:52 UTC

when trying to operate console from cli i got

[oVirt shell (connected)]# console VM1
unknown error: vncviewer: command not found

i needed to yum install tigervnc to have this function work


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

cli 2.2.1.2
Expected results:

vncviewer pkg will be part from cli instillation
 

Additional info:

Comment 1 Michael Pasternak 2012-03-14 13:54:24 UTC

Ofer,

don't we install it with the engine?

Comment 2 Ofer Schreiber 2012-03-14 15:07:46 UTC

(In reply to comment #1)
> Ofer,
> 
> don't we install it with the engine?

No.

Comment 3 Itamar Heim 2012-03-14 16:28:39 UTC

also, the CLI can be installed on any client, not related to locally on engine.

Comment 4 Itamar Heim 2012-03-14 16:29:34 UTC

I am not sure though this should be in requires, as would force pulling a vnc and spice clients. maybe just a better error message for user to install it?

Comment 5 Michael Pasternak 2012-03-15 15:36:58 UTC

+ absence of console rpm will fail cli installation, error message is
good enough here.