Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Describe the issue:
write a troubleshooting guide for satellite 6 with best practices, describe components and their logs.
some basic troubleshooting practices, guidelines to follow...
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