A test was added to the basic suite that attempts a "sudo kill" of the dirsrv process to check if dse.ldif is incorrectly removed. However, we can not assume that we have sudo ability during any test, let alone passwordless sudo.
Remove the sudo call in the test, and indicate the test should be run either with sudo if required to manipulate the dirsrv user, or it should be run as dirsrv itself.
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3185
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)