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.

Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server

Section Number and Name: Chapter 6, Section 20 and 20 a.

Describe the issue: Section 20 doesn't mention anything more than the generic verbiage "custom configs" but then when you see Section 20 a. it is exclusively concerned with Apache customizations. Also the Section 20 a. changes are missing the Include directive and when you do add them they cause an error on restart as the directory path being added does not yet exist.

Suggestions for improvement: Change paragraph 20 by modifying the paragraph's initial sentence from:

"If you have custom configurations"

-to-

"If you have custom Apache configurations" 

Additional information: This issue arose while assisting Bell Canada with upgrading their satellite from 6.1.9 to 6.2. They do have some customized foreman hooks in use and that paragraph with it's implication that it was important for "custom configurations" was mis-leading.

Hello 


Thank you for raising this bug

I wonder, should we say to back up the HTTP configs in the case that you have customer configs.

sorry, s/customer configs/custom configs/

(In reply to Chuck Mead from comment #0)
> Document URL:
> https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/
> installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server
> 
> Section Number and Name: Chapter 6, Section 20 and 20 a.
> 
> Describe the issue: Section 20 doesn't mention anything more than the
> generic verbiage "custom configs" but then when you see Section 20 a. it is
> exclusively concerned with Apache customizations. Also the Section 20 a.
> changes are missing the Include directive and when you do add them they
> cause an error on restart as the directory path being added does not yet
> exist.
> 

was that the XSend file error? How did you overcome it?

Thank you

All set, Stephen.

Thanks,
Brandi

Hello

This is now live on the customer portal

Thank you all