Bug #7516
closed
rudder-inventory-ldap and rudder-jetty don't stop their services on uninstall and rudder-slapd can fail to restart on upgrade
Added by Jonathan CLARKE almost 9 years ago.
Updated almost 9 years ago.
Description
As discovered in #7510, removing and reinstalling Rudder packages does not lead to a clean state. In particular, the rudder-inventory-ldap package does not stop slapd when it is removed, and the next time it is installed it also fails to restart slapd.
Two problems, two causes:
- Lack of a {pre,post}un scriptlet to stop slapd (at least on RPM systems)
- The restart command used doesn't call rudder-slapd forcestop, so it can silently fail if the process wasn't stopped, like if the PID file is missing, for example
- Blocks Bug #7510: rudder-upgrade fails when *re*installing Rudder added
- Related to Bug #7515: rudder-agent and rudder-slapd init scripts may fail to stop services if killall is missing or misbehaving added
- Subject changed from rudder-inventory-ldap doesn't stop rudder-slapd on uninstall and can fail to restart it on upgrade to rudder-inventory-ldap and rudder-jetty don't stop their services on uninstall and rudder-slapd can fail to restart on upgrade
Actually this should also be done for rudder-jetty.
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-packages/pull/820
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.17, 3.0.12 and 3.1.5 which were released today.
- Blocks deleted (Bug #7510: rudder-upgrade fails when *re*installing Rudder)
- Related to Bug #7510: rudder-upgrade fails when *re*installing Rudder added
Also available in: Atom
PDF