Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=820490 (Red Hat Enterprise Linux 6)
Description of problem: The "-c" option for sss_debuglevel utility is used when SSSD service runs with non-default config file. This option should work only with valid sssd.conf file. Currently, sss_debuglevel successfully updates the cache when any file is provided with "-c" option. It also works when non-existing files are provided with "-c" option which is not the expected behaviour. The utility should first verify the existence of config file, and then should also check if the given file is a genuine sssd.conf file. 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 using any existing file, by running the below command: # sss_debuglevel -c /etc/sysconfig/network 64 2. Verify if the debug_level value in config.ldb file is updated: # ldbsearch -H /var/lib/sss/db/config.ldb -b "cn=LDAP,cn=domain,cn=config" debug_level 3. Try to modify debug level using a non-existing file. # sss_debuglevel -c /root/non-existing_file 32 4. Verify if the debug_level value in config.ldb file is updated: # ldbsearch -H /var/lib/sss/db/config.ldb -b "cn=LDAP,cn=domain,cn=config" debug_level Actual results: The debug_level values get updated in the cache. Expected results: sss_debuglevel utility should display relevant error messages without updating the cache. Additional info:
Fields changed
blockedby: => blocking: => coverity: => feature_milestone: => keywords: => easyfix milestone: NEEDS_TRIAGE => SSSD 1.11.0 (LTM) tests: => 0 testsupdated: => 0 upgrade: => 0
keywords: easyfix =>
We should remove the -c option and instead auto-detect the config file in use by the running SSSD instance. On Linux, we can troll /proc for this information. We should make this lookup a separate function that can be replaced by a system-specific implementation on non-Linux systems, should they desire to do so.
proposed_priority: => Optional
This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.
milestone: SSSD 1.11.0 (LTM) => SSSD 1.12
This ticket wasn't required for 3 years already, so we can defer it..
changelog: => design: => design_review: => 0 fedora_test_page: => mark: => 0 milestone: SSSD 1.14 => SSSD Deferred review: => 0 selected: => sensitive: => 0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: easyfix
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/2370
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.