Integrate 6.1 Troubleshooting into prov guide about foreman-documentation

[Lennonka]

However, it is relevant in the scope of moving the manual into the docs.

[melcorr]

This may not happen in this format. We will have to uphold current documentation conventions of Red Hat. When I get through everything for this guide, I will look into this. An article might be best for this.

[lzap]

@ares actually brought this topic on our meeting today and we would like to be better in providing troubleshooting information and we agreed that the new documentation could be a new place for this. If this is a problem we can hide those sections from downstream, or even create a dedicated Troubleshooting Guide that would not be built downstream.

[melcorr]

The problem with Troubleshooting guides is that they very quickly become a dump of a thousand different things. Ideally the information is in the relevant sections of the doc so that the user doesn't need to troubleshoot. However, I know that is easier said than done. I will think about how best to approach this.

[melcorr]

Note to self: can we discuss "verification steps" in our next meeting.

[ekohl]

@Lennonka perhaps this is relevant in your process of reviewing the provisioning guide. If not, we can close it.

[Lennonka]

It isn't relevant in our current scope and I will not have the capacity to address this at least for half a year :(

[asteflova]

@Lennonka Is this something I could perhaps help with? (Feel free to say no if it's something you'd like to do yourself when you have the capacity.)

[Lennonka]

@asteflova Yes, help would be great. :)

[asteflova]

For TW uni course students: Estimated effort -- L.

To be implemented as Troubleshooting sections based on Modular documentation guide.