Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #701573 +++

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...

--- Additional comment from notting on 2012-01-04 13:29:03 EST ---

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.)

--- Additional comment from notting on 2012-01-04 14:23:24 EST ---

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.

Built as 1.3.49.3-1.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When an LSB initscript was enabled, scripts with dependencies on the script being enabled would not always be set up correctly, due to a bug in how LSB dependencies are handled. chkconfig has been changed to properly calculate script dependencies on scripts being installed, and now enabling of LSB services works correctly.

Comment#5 => Verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0873.html