Bug 1092178

Summary:	RPM pre-uninstall scriptlet should not touch running services
Product:	[Community] GlusterFS	Reporter:	Robert Lanning <lanning>
Component:	build	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, kkeithle, ndevos
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-27 17:18:52 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 Robert Lanning 2014-04-28 22:28:42 UTC

Description of problem:
These RPMs cannot be used in production, as they touch running services, without consulting the systems admin.

1) There is not enough logic to know everything that must be done for a clean restart. (rc script/upstart/systemd/puppet/chef/cfengine/... controlled)

2) Upgrading services is a two stage process (only stage "b" causes an outage)
   a) update files (standard RPM install)
   b) restart services (Unknown environmental dependencies)

The only rule is that "a" comes before "b".  There could be days between the two, depending on environmental requirements (including political ones.)

So, for everyone that is running their production cluster properly, they must rebuild the RPMs to omit the pre-uninstall scriptlet.  This make the current RPM set unusable to anyone but experimenters, or those that don't care about end user experiences or production outages.

Unix design philosophy: Do one thing and do it well.
Software Package: Install software only

Please remove pre-uninstall scriptlet.

Version-Release number of selected component (if applicable):
3.5.0-2

How reproducible:
Very

Steps to Reproduce:
1. Upgrade RPM on any running node
2. 
3.

Actual results:
Services are restarted

Expected results:
Services should not be started/stopped or restarted.

Additional info:

Comment 1 Niels de Vos 2016-01-19 12:22:15 UTC

Some users expect the services to be restarted, others dont. This is a conflict that we can only resolve by making the restart a configurable option.

It would be good to have an option in /etc/sysconfig/gluster that influences the RPM scriptlets and does not restart when the option in enabled.

Fedora packaging requires restarting of the services when updates are installed. This should probably stay the default. (Also, most sysadmins that I know only install updates during maintenance windows where systems are temporarily taken offline.)

Comment 2 Yaniv Kaul 2019-04-27 17:18:52 UTC

If Fedora packaging allow it, I assume we should keep it.