#1327 When multiple values are assigned, sss_debuglevel should display a usage message
Closed: Fixed None Opened 8 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=820362 (Red Hat Enterprise Linux 6)

Description of problem:
Upon executing "sss_debuglevel" with multiple HEX values, e.g. NEW_DEBUG_LEVEL
= 0xfff0 0xbbb1, it updates debug levels in config.ldb file with value: 0xfff0.
The utility accepts the first value and update the cache accordingly. However,
instead of accepting the value, in this case sss_debuglevel should display a
usage message.

Version-Release number of selected component (if applicable):
sssd-1.8.0-22.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Modify debug level by executing the below command:
   # sss_debuglevel 0xFFF0 0xBBB1
2. Verify debug_level value in config.ldb file:
   # ldbsearch -H /var/lib/sss/db/config.ldb -b "cn=LDAP,cn=domain,cn=config"
debug_level

Actual results:
config.ldb file gets successfully updated with debug_level: 0xfff0 without
displaying any error/usage message.

Expected results:
sss_debuglevel utility should display a usage message.

Additional info:

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
keywords: => easyfix
tests: => 0
testsupdated: => 0
upgrade: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

milestone: SSSD Deferred => SSSD 1.11.0 (LTM)

Fields changed

proposed_priority: => Nice to have

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: SSSD 1.11.0 (LTM) => SSSD 1.10 beta

Fields changed

owner: somebody => mzidek

Fields changed

patch: 0 => 1

Fields changed

status: new => assigned

master: 31ddfc3

resolution: => fixed
status: assigned => closed

For tickets already closed set the field to "Want"

selected: => Want

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.10 beta

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

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