-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lib389 remove_ds_instance() does not remove systemd units #2671
Comments
Comment from mreynolds (@mreynolds389) at 2018-04-05 17:44:15 Metadata Update from @mreynolds389:
|
Comment from firstyear (@Firstyear) at 2018-04-08 01:26:13 Great find! I'll have a look at this soon. If it's urgent, @droideck can probably help :) |
Comment from stlaz at 2018-04-10 14:56:57 I guess it's alright, I'd only like to have freeipa/freeipa#1563 working rather sooner than later but that's just because I like tests passing. It's not going to be in Fedora 28 so it's not critical. |
Comment from spichugi (@droideck) at 2018-04-18 16:23:32 Metadata Update from @droideck:
|
Comment from spichugi (@droideck) at 2018-04-19 14:50:11 Metadata Update from @droideck:
|
Comment from mreynolds (@mreynolds389) at 2018-04-20 16:03:28 Metadata Update from @mreynolds389:
|
Comment from spichugi (@droideck) at 2018-04-20 17:31:00 |
Comment from spichugi (@droideck) at 2018-04-20 17:31:10 Metadata Update from @droideck:
|
Comment from firstyear (@Firstyear) at 2018-04-24 02:57:33 @droideck Hey there. I think there is an issue with your systemctl call. What happens when you run dsctl inst remove twice. You should be able to run the remove as many times as you like safely, to remove the content. I think the current way you have here, if the systemctl isn't there it'll throw an exception perhaps? Can we check this? |
Comment from spichugi (@droideck) at 2018-04-24 09:15:32 Sure, I've checked. We don't have any problem here.
And regarding the twice removal of 'dsctl instance remove', we are also okay:
|
Comment from firstyear (@Firstyear) at 2018-05-14 05:08:11 Great! Ack from me. Great stuff. |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49612
Issue Description
When running
remove_ds_instance()
, it does not remove the systemd files that identify this instance, namely:This makes systemd think a DS instance still exist and it also thinks that it can try to start one.
Also, in previous DS versions, the
/etc/dirsrv/slapd-INSTANCE
would have been moved to/etc/dirsrv/slapd-INSTANCE.removed
. This does not happen now. Was this a design decision?Package Version and Platform
Steps to reproduce
Actual results
Expected results
The symlinks get removed and the directory moved to
*.removed
The text was updated successfully, but these errors were encountered: