Description of problem:

vdsm's rpm package currently installs it enabled by default. This means that after a reboot, it configures the system and starts vdsm.

This is not very useful, in itself, and I think most sysadmins would agree that it's unexpected.

Version-Release number of selected component (if applicable):
Since oVirt 3.6, as part of systemd support.

How reproducible:
Always

Steps to Reproduce:
1. Install vdsm
2. Reboot
3.

Actual results:
vdsm configures the system and starts, after reboot

Expected results:
vdsm does nothing until manually configured and enabled, usually by adding the machine as a host to an oVirt engine.

Additional info:

I personally also ran into a specific problematic flow during development phase of oVirt 4.4, which was a result of this:

1. Installed some version of vdsm, took a snapshot of the machine, did some work, tests, etc. on it
2. Reverted to the snapshot, booted the machine, ran 'dnf update', tried to deploy hosted-engine.

This failed, because newer versions of libvirt and vdsm were incompatible with the changes done by vdsm-tool of the version installed in step (1.), during the reboot of step (2.).