Assigning to Russell for review.

Hi Russell,

To try to answer your questions:

* I think that the scale should be relatively modest. We already have a large set of articles to help customers troubleshoot their issues. A troubleshooting guide would necessarily be a distillation of those articles into a a subset of common problems that present themselves similarly and have an established resolution that's simple enough for customers to do it unaided.
* I think that it makes more sense to include a "troubleshooting" section in each guide, to help users fix the problems they've encountered during one process before moving to the next. This also lets us start small by adding troubleshooting for one process at a time (I suggest the virtualization guide as a start)
* I think that we need to keep the troubleshooting work relatively low-effort. I see it as working with GSS to identify the kinds of issues I mentioned in the first bullet and including the symptoms and resolution steps, not as a comprehensive guide to what can go wrong with Satellite and how to fix it.

Does that make sense?

Thanks,
Steve

Hi Steve,

I do not have full visibility over the bug, seems.

I think that the two main topic has to be addressed:
1) a list of common commands to be performed in case of issue (like katello-service restart, df -h, ...);
2) a set of command that, with a positive match, will address to the solution already written.

My 2 cents,
Daniele

Returning to the default assignee and status 'NEW' to be triaged again as the schedule and priorities allow.