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

Bug 977306

Summary:	Password validity time related information is missing in "console.vv" for rhevm 3.2.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Udayendu Sekhar Kar <ukar>
Component:	ovirt-engine	Assignee:	Frantisek Kobzik <fkobzik>
Status:	CLOSED ERRATA	QA Contact:	Lukas Svaty <lsvaty>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.0	CC:	adahms, iheim, lpeer, mavital, michal.skrivanek, rbalakri, Rhev-m-bugs, rpai, sherold, srevivo, ukar, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:	ovirt-3.5.0-alpha1	Doc Type:	Enhancement
Doc Text:	This enhancement adds information about password validity to console.vv files. It affects 'Native client' console invocation for SPICE and VNC.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-11 17:53:29 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:
Bug Depends On:
Bug Blocks:	1142923, 1156165

Comment 1 Michal Skrivanek 2013-07-12 09:41:10 UTC

the password validity time is not for the client, it's being set on the host, hence it's not part of the configuration file for virt-viewer.
We can add that as a comment there, though I don't see much benefit in that - if you store the file and look later those 120s it won't have any relevancy

Also, would you please explain the customer the intent of this feature? They should associate the file with a wrapper script or wait till 3.3 for proper RHEL virt-viewer supporting it directly

Comment 4 Lukas Svaty 2014-08-12 08:26:21 UTC

verified in ovirt-rc1

Comment 6 errata-xmlrpc 2015-02-11 17:53:29 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html