Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2040621

Summary:	[Improvement] Enable sssd backtrace using sssctl
Product:	Red Hat Enterprise Linux 8	Reporter:	Abhijit Roy <abroy>
Component:	sssd	Assignee:	sssd-maint
Status:	CLOSED WONTFIX	QA Contact:	sssd-qe
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	aboscatt, atikhono, ekeck, grajaiya, jhrozek, lslebodn, mzidek, pbrezina, peter.vreman, tscherf
Target Milestone:	rc	Keywords:	Improvement, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	All
Whiteboard:	sync-to-jira
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-31 17:46:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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