Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1442727
Description of problem: This is an Idea that can reduce number of cases to be raised. Many times cases are opened for an ipa installation/preparation command when fails. Cu provides Error log from console, Engineer finds the KCS articles links to case. How good it would be if after command failure logs, KCS Articles/Installation Videos(If available)/Config Creator Tool links are provided before-hand. Its less bit likely that Cu opens the KCS/Videos & his Issue gets resolved & case is not opened by itself. I hope this would be bit easy task, would involve Printing URL of KCS/Videos/Config Creator Tool[Wherever applicable] whenever relevant function call returns not-ok. Similar code can be written for other services eg: sssd(where-ever Applicable) Version-Release number of selected component (if applicable):7 How reproducible: NA Steps to Reproduce:NA 1. 2. 3. Actual results:NA Expected results:NA Additional info:NA
Metadata Update from @pvoborni: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1442727
Metadata Update from @rcritten: - Issue set to the milestone: FreeIPA 4.7.1 (was: FreeIPA 4.7)
FreeIPA 4.7 has been released, moving to FreeIPA 4.7.1 milestone
From the BZ:
We discussed this request internally and did not think this is the best approach, especially given IdM is based on FreeIPA upstream project. To make this solution truly open, we would need to have different links in upstream FreeIPA and downstream version, for example and carry it in patches.
Instead, we thought that the right way was to enhance Red Hat Customer portal analysis capabilities. I would suggest either an extension in Red Hat Insights or existing bug description/log analysis that happens when Case is inserted and that should recommend the best articles based on the contents. IdM team can help with the log analysis, should this be found as the best approach.
Based on above, I think we can close the bug or move to other component, based on the preferred solution.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.