Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1373420
Created attachment 1198131
Description of problem:
sss_override user-export fails
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up an LDAP provider
2. Create an user override:
3. Restart sssd
4. Try to export the user overrides
# sss_override user-export /var/lib/sss/backup/sssd_user_overrides.bak
# echo $?
# ls -la /var/lib/sss/backup/sssd_user_overrides.bak
-rw-r--r--. 1 root root 0 6. Sep 09:04
sss_override should not fail to export.
It would be great, if sss_override user-export tells the user when it fails. I
only discovered this bug, because I wanted to remove the SSSD cache. Otherwise
I had not seen that it generates just an empty file and fails. The "sssctrl
cache-remove" command validates the result of the backup:
# sssctl cache-remove
SSSD must not be running. Stop SSSD now? (yes/no) [yes]
Creating backup of local data...
SSSD backup of local data already exist, override? (yes/no) [no] yes
Error while executing external command
Unable to export group overrides
Unable to create backup of local data, can not remove the cache.
design_review: => 0
mark: no => 0
owner: somebody => mzidek
patch: 0 => 1
review: True => 0
testsupdated: => 0
Works in 1.13, it is a regression.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1373420 (Red Hat Enterprise Linux 7)
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1373420 1373420] => [https://bugzilla.redhat.com/show_bug.cgi?id=1373420 1373420], [https://bugzilla.redhat.com/show_bug.cgi?id=1373420 1373420]
milestone: NEEDS_TRIAGE => SSSD 1.14.2
resolution: => fixed
status: new => closed
version: => 1.14.0
Metadata Update from @mzidek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.14.2
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.