Bug 701573

Summary:	sysv service start prio not adjusted when a Should-Start dep gets enabled
Product:	[Fedora] Fedora	Reporter:	Hans de Goede <hdegoede>
Component:	chkconfig	Assignee:	Bill Nottingham <notting>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	notting, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	chkconfig-1.3.57-1.fc16	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	771741 (view as bug list)		Environment:
Last Closed:	2012-01-15 20:06:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	771741

Description Hans de Goede 2011-05-03 09:06:14 UTC

Recently the iscsi sysv init script has grown the following deps:
Should-Start:      tgtd
Should-Stop:       tgtd

So that logging in to locally hosted iscsi targets works properly, this means
it should be ordered after tgtd, but if I disable iscsi + tgtd then:
1) enable iscsi, gets position 13
2) enable tgtd gets pos 24, iscsi stays at position 13

Then enabling / disabling some other service (tried iscsid) moves iscsi to 25,
but this should have happened as soon as tgtd was enabled...

Comment 1 Bill Nottingham 2012-01-04 18:29:03 UTC

The problem isn't necessarily 'Should-Start' dependencies.

The algorithm currently is:

a) resolve all existing scripts
b) resolve our target script

So, if something in set A has a dep on what's being enabled in B, and B gets moved, there's no step to cover for that.

(This is what happens when the algorithm isn't a real dependency solver.)

Comment 2 Bill Nottingham 2012-01-04 19:23:24 UTC

This is fixed in http://git.fedorahosted.org/git/?p=chkconfig.git;a=commitdiff;h=679231f31c775326e2c5e78c1821149ded1dbb60, although you don't want to be cherry-picking that... grab the whole series of recent changes.

Comment 3 Fedora Update System 2012-01-04 20:27:24 UTC

chkconfig-1.3.57-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/chkconfig-1.3.57-1.fc16

Comment 4 Fedora Update System 2012-01-05 21:05:27 UTC

Package chkconfig-1.3.57-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing chkconfig-1.3.57-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-0143/chkconfig-1.3.57-1.fc16
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-01-15 20:06:09 UTC

chkconfig-1.3.57-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.