#1788 [RFE] Create a command line tool to return the current debug level of sssd
Closed: wontfix 4 years ago by pbrezina. Opened 11 years ago by dpal.

https://bugzilla.redhat.com/show_bug.cgi?id=895530

A command line tool to display the current debug level of sssd is missing.

Following BZ#766904, there is now a tool to change sssd debug level on the fly.
Knowing the current debug level would help to determine what the new value
would be.

For example, get an option to sss_debuglevel to display current debug level.

I think adding a new option (-p/--print) to sss_debuglevel would be the best way forward.

We might also consider moving sss_debuglevel from -tools to the code sssd package, which is what we already did with sss_cache.

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta

Fields changed

summary: Create a command line tool to return the current debug level of sssd => [RFE] Create a command line tool to return the current debug level of sssd
type: defect => enhancement

See #1800 for the proposed solution for this.

Fields changed

changelog: =>
keywords: => Status
review: => 0

Fields changed

mark: => 1

Fields changed

owner: somebody => preichl

We agreed to provide a DBus API for SSSD status first and build a simple utility atop it.

Downstream no longer requires this RFE. Moving to backlog.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

This is part of Pavel's status tool

milestone: SSSD 1.13 backlog => SSSD 1.14 beta
sensitive: => 0

The status tool is there, but this piece of functionality is still to be merged.

milestone: SSSD 1.14 beta => SSSD 1.14.0

1.14.0 should be released no later than Wednesday next week, this ticket should not block the 1.14.0 release.

milestone: SSSD 1.14.0 => SSSD 1.14.1

We need to release 1.14.1 soon, therefore moving to 1.14.2.

milestone: SSSD 1.14.1 => SSSD 1.14.2

We should transition the 1.14 branch to the maintenance mode, moving to triage to discuss which milestone to fix this ticket at.

milestone: SSSD 1.14.2 => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.16 beta

Metadata Update from @dpal:
- Issue assigned to preichl
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from 0)
- Custom field mark adjusted to on (was: 1)
- 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: Canditate to close

4 years ago

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)

4 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/2830

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