Bug 2040621 - [Improvement] Enable sssd backtrace using sssctl
Summary: [Improvement] Enable sssd backtrace using sssctl
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.6
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: sssd-maint
QA Contact: sssd-qe
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-14 10:00 UTC by Abhijit Roy
Modified: 2023-05-31 17:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-31 17:46:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-108164 0 None None None 2022-01-14 10:04:42 UTC
Red Hat Issue Tracker SSSD-4259 0 None None None 2022-01-17 08:46:18 UTC

Description Abhijit Roy 2022-01-14 10:00:55 UTC
Description of problem:

1. Enable sssd backtrace using sssctl
 
2. Extend sssctl with a new option to enable debug_backtrace feature, just like it can already adjust the debug_loglevel

3. Sales team is not involved in this RFE

4. Cus can help us in testing.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Alexey Tikhonov 2022-01-14 10:14:49 UTC
Hi,

(In reply to Abhijit Roy from comment #0)
>  
> 2. Extend sssctl with a new option to enable debug_backtrace feature

What is the expectation:
 (1) permanent change of sssd.conf via sssctl
or
 (2) temporarily change (until next restart of sssd)
?

Comment 4 Abhijit Roy 2022-01-14 10:17:30 UTC
Hello,

temporarily change (until next restart of sssd)

Having new debug_backtrace_enabled=false in the sssd.conf to prevent flooding the log files there shall be a possibility to enable temporarily the debug_backtrace feature only when needed.

Comment 6 Andre Boscatto 2023-05-31 17:46:23 UTC
Please know that we carefully considered and evaluated your request and its potential impact on our product roadmap, market demand, and overall strategy.

While we understand that addressing enhancements, bugs, and issues is critical for ensuring the quality and reliability of our product, we need to balance these priorities with our long-term goals and resource constraints. Unfortunately, we cannot address this request at this time as it does not align with our product vision and strategy, and keeping it in the backlog would be misleading and give the false impression that we will address it in the future, thus we are closing it.

Although we cannot address this specific request, we encourage anyone to collaborate and contribute to the upstream communities, as this approach enhances the flexibility, scalability, and customization of our solution while maintaining its security and stability.

We apologize for any inconvenience this may cause, and we understand that it can be frustrating when requests/expectations are not met. However, we hope that you can appreciate that we must balance our priorities with our long-term goals and resource constraints.

Please be aware that while you are welcome to open a new support case or reopen this request, we cannot guarantee that it will be addressed due to resource constraints and the prioritization of other requests.

Once again, thank you for taking the time to share feedback with us, and we look forward to continuing to work together to deliver the best possible solution, supporting in any way we can.

Thank you for understanding,

André Boscatto
Product Owner - Identity and Access Management Department


Note You need to log in before you can comment on or make changes to this bug.