Bug 1033625

Summary:	[RFE] Add an explicit request for having services started at boot
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Setup.Engine	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED DEFERRED	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	low	Docs Contact:
Priority:	low
Version:	---	CC:	bazulay, bugs, didi, lveyde, rbalakri, Rhev-m-bugs, rmartins, sbonazzo, srevivo, stirabos, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Add an explicit request for having services started at boot Reason: Result (if any):	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-07 21:46:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sandro Bonazzola 2013-11-22 14:17:41 UTC

while discussing http://gerrit.ovirt.org/#/c/20736/1 it has been pointed out that (citing Alon):

We should not play with services startup state during an upgrade.
Auto enable service during setup is by it-self kind of violation, probably we need to ask user if he wish us to auto start the required service.
[...]
But on update we should not touch service startup state unless it is part of upgrade, for example we split engine into two services, initial service is marked to be started at boot, so we mark both to be started.

I think that it is right.

https://fedoraproject.org/wiki/Packaging:Systemd#Why_don.27t_we....
 Why don't we....
    Start the service after installation? 
 Installations can be in changeroots, in an installer context,
 or in other  situations where you don't want the services autostarted. 

https://fedoraproject.org/wiki/Packaging:SysVInitScript#Why_don.27t_we....
 Why don't we....
    run 'chkconfig <service> on'? 
 If a service should be enabled by default, make this the default in the init
 script. Doing otherwise will cause the service to be turned on on upgrades
 if the user explicitly disabled it.
 Note that the default for most network-listening scripts is off.
 This is done for better security.
 We have multiple tools that can enable services, including GUIs.

Comment 1 Sandro Bonazzola 2015-03-17 16:26:22 UTC

Yaniv, can you check if this is desired / wanted at pm level?

Comment 2 Yaniv Lavi 2015-03-24 09:47:25 UTC

(In reply to Sandro Bonazzola from comment #1)
> Yaniv, can you check if this is desired / wanted at pm level?

If the engine service is disabled (off or stopped) before upgrade, we need to keep that behaviour during upgrade. 
If any service is disabled we should also keep it the same way.

On clean install we can ask the user to start the needed services automatically. If the user refuses, we should install with the engine\reports\dwh services stopped and off on boot.

Comment 3 Sandro Bonazzola 2015-04-02 07:05:08 UTC

Thanks Yaniv, requirements are clear.

Comment 4 Yaniv Kaul 2017-06-07 21:46:07 UTC

Closing old RFEs. Please reopen if relevant.