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.

The guide currently includes a troubleshooting appendix listing common problems + their solutions: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/trouble.html

To complement this, we need guidelines for *general* troubleshooting: for example, advice on how to investigate the problem, how to find out where in the architecture it occurs, etc.
These guidelines might also include more architecture-related information so that users can better understand the framework, which could put them into a position where they can fix issues on their own.

The current proposal is to create a decision tree based on the situation in which the problem occurred (for example, server/replica/client installation, migration, command doesn't work, etc.) + steps to further investigate the problem (which logs to check, possibly links to solutions if they are obvious at this stage, what to do when the logs don't show anything, etc.).

As part of this BZ, I will also review the current files and logs reference material (current chapter Identity Management Files and Logs). Some of this material will need to be removed to prevent duplication with the new troubleshooting content.

I have all the feedback I need for now. Now it's up to me to implement it.

All available feedback implemented. New updates are waiting for another SME review.

Alexander's blog post about the changes that affect some of the troubleshooting procedures: https://vda.li/en/docs/freeipa-debug-privsep/  I changed the procedures based on the article, and I'm currently waiting for more details as noted in c#10.

I hit a bit of a dead end with this BZ. The product behavior unexpectedly changed while I was working on it, which affected a few of the planned procedures; for a few others, I failed to get the required information.

I wrote seven troubleshooting procedures that have been reviewed and acked: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/trouble-general.html This should be sufficient to consider this BZ done.

We can always add more if there is new information.