#3180 sss_cache -r option does not print error message if more than one argument is supplied
Closed: Fixed None Opened 4 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1374650

Description of problem:
While executing sss_cache command to invalidate multiple sudo rule with '-r'
option it does not print any error about multiple sudo  rules mentioned.
Command executes with invalidating first rule mentioned and exit status '0' .

Environment : Configure sssd as ldap-client against LDAP-server such as
OpenLDAP or IPA or 389-DS.
Store sudo rules on LDAP-server. And configure sssd-client system to fetch sudo
rules from LDAP server.


Version-Release number of selected component (if applicable):
sssd-1.14.0-27.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. # sss_cache -r sudo_rule_1 sudo_rule_2

Actual results:
Command exits with exit_status '0'

Expected results:
Command should print warning or error message about incorrect syntax. It could
also direct toward Usage option. Something like:

# sss_cache -r sudo_rule_1 sudo_rule_2

Please use only one object to invalidate.

Additional info:

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD Deferred
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

keywords: => easyfix

milestone: SSSD Deferred => SSSD 1.14.2
resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.14.2

3 years ago

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/4213

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.

Login to comment on this ticket.

Metadata