Bug 1256704

Summary: Feature req: exit with error in case of absence /dev/virtio-ports/com.redhat.spice.0
Product: Red Hat Enterprise Linux 7 Reporter: Andrei Stepanov <astepano>
Component: spice-vdagentAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED ERRATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: cfergeau, dblechte, marcandre.lureau, rbalakri, rduda, sherold, tpelka
Target Milestone: rcKeywords: FutureFeature
Target Release: 7.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spice-vdagent-0.14.0-11.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 03:42: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:

Description Andrei Stepanov 2015-08-25 09:55:41 UTC
Suppose host was somehow configured without spicevmc

Spice-vdagent exits silently without any notification 

It is good to have somewhere info why spice-vdagent has failed to start.

strace shows me such info:

3685  stat("/dev/virtio-ports/com.redhat.spice.0", 0x7fff8c3c3e30) = -1 ENOENT (No such file or directory)
3685  exit_group(0)                     = ?
3685  +++ exited with 0 +++

Why retcode is 0? spice-vdagent failed to start.

Comment 2 Christophe Fergeau 2015-09-07 15:12:27 UTC
Sent http://lists.freedesktop.org/archives/spice-devel/2015-September/021856.html upstream

Comment 4 Mike McCune 2016-03-28 23:26:37 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 8 errata-xmlrpc 2016-11-04 03:42: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/RHBA-2016-2323.html