Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=813000 (Red Hat Enterprise Linux 6)
Description of problem: When sss_cache is executed against a non-existing user/group name, it should return at least a warning and a non-zero exit code. Version-Release number of selected component (if applicable): sssd-1.8.0-22.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Execute the below step against an unknown user/group: # sss_cache -u <some_user> -g <some_group> Actual results: Users/groups in the cache remains unchanged and the command returns a 0 exit code. Expected results: A warning message and a non-zero exit code. Additional info:
Fields changed
blockedby: => blocking: => coverity: => feature_milestone: => owner: somebody => jhrozek patch: 0 => 1 status: new => assigned tests: => 0 testsupdated: => 0 upgrade: => 0
Fixed in master: da0b829
I'll leave this ticket in NEEDS_TRIAGE until our weekly meeting so that we can decide whether we want to back port any of the error message related tickets to 1.8.x
milestone: NEEDS_TRIAGE => SSSD 1.9 beta
resolution: => fixed status: assigned => closed
Metadata Update from @dpal: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.9.0 beta 1
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: - https://github.com/SSSD/sssd/issues/2347
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.
Login to comment on this ticket.