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://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/managing_content/index?lb_target=preview#Creating_a_Remote_File_Type_Repository_content-management


Section Number and Name: 

16.3. Creating a Remote File Type Repository

Procedure part


Describe the issue: 

The first and second steps in the procedure part refer to RHEL 7-related Satellite Client repo

But we don't provide RHEL 8 based instructions there. There are two reasons why we need it:

A) Customers may want to use an RHEL 8 based apache server to create the file repo.

B) Customers may want to use the Satellite 6.12 server itself to host the repo and the baseOS would be RHEL 8.


Suggestions for improvement: 


Include name of the repo and package that will be required for RHEL 8. 

Refer to https://bugzilla.redhat.com/show_bug.cgi?id=2116871 for more info.


Additional information: 

NA

PR Created with the changes approved by SME in the google docs:
https://docs.google.com/document/d/1fnt3F8JG_iuRwvimn3p5oOHzRWYgCgIMd9KsYqAtXW8/edit?usp=sharing

PR:
https://github.com/theforeman/foreman-documentation/pull/1650

Regards,

Hello,

Changes have been made to the document and all the PRs mentioned below are merged into the respective branches for changes to take effect. 

- For Foreman 3.4, see https://github.com/theforeman/foreman-documentation/pull/1722
- For Foreman 3.1, see https://github.com/theforeman/foreman-documentation/pull/1723
- For Foreman 3.3, see https://github.com/theforeman/foreman-documentation/pull/1671

Thank you ekohlvan, ehelms, and zuansorg for helping me conclude this throughout the process. 

Here is the link to the published doc: 
https://theforeman-foreman-documentation-preview-pr-1671.surge.sh/3.3/Managing_Content/index-satellite.html#Creating_a_Custom_File_Type_Repository_in_a_Local_Directory_content-management

No more updates are pending on this issue hence closing it for now. In case any more updates are required, feel free to reopen the same of create a new case. 

Thank you :)