Bug 145869

Summary:	iiimf-server starts on boot after update
Product:	[Fedora] Fedora	Reporter:	Jeff Moe (jebba) <moe>
Component:	im-sdk	Assignee:	Yu Shao <yshao>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	eng-i18n-bugs, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-01-23 00:50:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Moe (jebba) 2005-01-22 21:52:15 UTC

Description of problem:
After an update of iiimf-server it starts on boot, even when the
previous version was set to not start on boot. So if iiimf-server is
installed, but not in use, a user who thinks they have it disabled
will have it re-enabled at boot when they upgrade.

Version-Release number of selected component (if applicable):
iiimf-server-12.1-10.FC3.i386.rpm and earlier

How reproducible:
Get an older version of iiimf-server, turn it off on boot, upgrade.


Steps to Reproduce:
1.
rpm -U --oldpackage iiimf-server-[older one]

2.
chkconfig --del iiimf

3.
rpm -U  iiimf-server-12.1-10.FC3.i386.rpm

4.
chkconfig --list | grep iiim  [shows iiim on]


Actual results:
iiim is set to start on boot.

Expected results:
iiim is left at it's previous setting to not start on reboot. Apache,
for example, honors it's previous setting.


Additional info:
This is similar to a cups bug that was fixed a couple days ago:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145629

Comment 1 Jeff Moe (jebba) 2005-01-23 00:50:43 UTC

Sorry, should be using
chkconfig iiim off

not --del