Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1518411 - enable spice-vdagentd.socket by default
enable spice-vdagentd.socket by default
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-release (Show other bugs)
7.5
Unspecified Unspecified
unspecified Severity unspecified
: beta
: ---
Assigned To: Lubos Kocman
Release Test Team
:
Depends On:
Blocks: 1340160
  Show dependency treegraph
 
Reported: 2017-11-28 15:47 EST by Jonathon Jongsma
Modified: 2018-04-10 06:21 EDT (History)
6 users (show)

See Also:
Fixed In Version: redhat-release-server-7.5-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 06:20:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0700 None None None 2018-04-10 06:21 EDT

  None (edit)
Description Jonathon Jongsma 2017-11-28 15:47:31 EST
For RHEL 7.5, spice-vdagent slightly changed its systemd service configuration and added support for systemd socket activation. The service and socket are both only active if a specific virtio port device exists (i.e. it is running within a vm), so it can be safely enabled by default.

The unit that should be added is /lib/systemd/system/spice-vdagentd.socket

(reference Bug #876237 for the previous change where the .service file was added to the list of default enabled units)
Comment 1 Jan Synacek 2017-12-04 02:37:32 EST
Such change should be done in the presets.
Comment 2 Lubos Kocman 2017-12-04 04:57:22 EST
Develacking+ I'll need rest of acks guys. Setting target milestone to beta

Lubos
Comment 9 errata-xmlrpc 2018-04-10 06:20:23 EDT
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://access.redhat.com/errata/RHEA-2018:0700

Note You need to log in before you can comment on or make changes to this bug.