Description of problem:

I would expect daemons are present in `chkconfig --list' output. IIUC usually daemons are "registered" there with `chkconfig --add $daemon' (like postfix for example) during rpm installation. Startup/stopping is based on admin's need (`chkconfig $daemon on').

This said, I expect most admins know 'on/off' knobs of 'chkconfig', but they could be surprised not seeing all ovirt daemons there, as '--add/--del' is usually done by rpm mgmnt, and because of that they could even not know '--add/--del' :)

[root@jb-rh34 ~]# chkconfig --list | grep ovirt
ovirt-engine    0:off   1:off   2:on    3:on    4:on    5:on    6:off
ovirt-guest-agent       0:off   1:off   2:off   3:on    4:off   5:on    6:off
ovirt-websocket-proxy   0:off   1:off   2:on    3:on    4:on    5:on    6:off
[root@jb-rh34 ~]# ls /etc/init.d/ovirt-*
/etc/init.d/ovirt-engine       /etc/init.d/ovirt-engine-notifier  /etc/init.d/ovirt-websocket-proxy
/etc/init.d/ovirt-engine-dwhd  /etc/init.d/ovirt-guest-agent

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

How reproducible:
ovirt-engine-setup-3.4.0-0.7.beta2.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-3.4.0-0.7.beta2.el6.noarch
ovirt-engine-setup-base-3.4.0-0.7.beta2.el6.noarch
ovirt-engine-setup-plugin-websocket-proxy-3.4.0-0.7.beta2.el6.noarch
ovirt-engine-setup-plugin-ovirt-engine-3.4.0-0.7.beta2.el6.noarch

Steps to Reproduce:
1. install ovirt-engine
2. configured notifier
3. chkconfig --list | grep ovirt-engine-notifier

Actual results:
ovirt-engine-notifier is not known to chkconfig

Expected results:
just add all ovirt daemons but do not put them 'on' - this should be done by engine-setup or on admin's explicit request (chkconfig $daemon on)

Additional info:
also applies to dwh