Bug 126481
Summary: | RFE: add info on how to handle broken DNS | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Patrick C. F. Ernzer <pcfe> |
Component: | Documentation | Assignee: | Clay Murphy <cmurphy> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | herrmann, rhn-bugs, tao |
Target Milestone: | --- | Keywords: | Documentation, FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-15 14:36:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 128275 |
Description
Patrick C. F. Ernzer
2004-06-22 10:15:52 UTC
Hi Patrick. We already cover this solution within the Troubleshooting chapter. See: https://rhn.redhat.com/help/satellite/host-not-found.html I didn't realize DNS errors were so common during installation. We already stipulate working DNS in the Additional Requirements section. Will it suffice to mention the error within the appropriate section of the Installation chapter (registration confirmation) with a cross-reference to the above troubleshooting item for the solution? This way, we avoid duplicate steps and isolate troubleshooting to a single area. What'cha think? Regardless of the change we agree upon, I'll address in the next release. Aligning to the 350 doc tracking bug and updating the version and cust-facing fields. Clay, my bad, should have checked the Troubleshooting chapter. Yes, pointing to that part of the Troubleshooting chapter in te Installation chapter is absolutely sufficient. (I see broken DNS with about 10-20% of the customers, mostly it is reverse-lookup not working) Once the link to the relevant troublesooting section is made, I will move this bug (or just make a new one), as in the long run I'd like to have a dialog pop up for those users not even reading the Installation Chapter. Moving blocker from the 350 hosted doc bug to the 350 sat doc bug, since that is when this documentation change will appear. Alright, I've addressed in the brand new Installation chapter by adding a line to the RHN Entitlement Certificate step that reads, "If you receive errors related to DNS, ensure your Satellite is configured correctly. Refer to the (cross-reference to the above-mentioned Troubleshooting section)." Looks good on QA. |