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.
Bug 1206788 - [doc] Incorrect /var/www/html/content location for content isos
Summary: [doc] Incorrect /var/www/html/content location for content isos
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs User Guide
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Megan Lewis
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On: 1200617
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2015-03-28 15:32 UTC by Shannon Hughes
Modified: 2019-09-26 16:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-24 12:40:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shannon Hughes 2015-03-28 15:32:09 UTC 
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/User_Guide/Importing_Content_to_the_Disconnected_Satellite_Server.html

Section Number and Name: 4.3.4. Importing Content to a Disconnected Satellite Server

Describe the issue: During the steps for unpacking the content iso we give an example to use http://localhost/content. By default the content isos unroll to the top level directory of content but placing this content in /var/www/html directory will not work since the order of apache conf files when loaded with override the default /var/www/html

[root@satellite conf.d]# grep DocumentRoot * | grep -v ":#"
05-foreman.conf:  DocumentRoot "/usr/share/foreman/public"
05-foreman-ssl.conf:  DocumentRoot "/usr/share/foreman/public"
15-default.conf:  DocumentRoot "/var/www/html"
25-puppet.conf:  DocumentRoot "/etc/puppet/rack/public/"


note in above snippet the 05-foreman.conf will beat out 15-default.conf

15-default.conf will additionally include more conf files: 

<IfVersion < 2.4>
  Include /etc/httpd/conf.d/05-foreman.d/*.conf
</IfVersion>
<IfVersion >= 2.4>
  IncludeOptional /etc/httpd/conf.d/05-foreman.d/*.conf
</IfVersion>


this will read in additional files that setup the /pub directory. 


Suggestions for improvement: 

Use the /pub directory for iso content or fix the apache conf files to allow use of the default /var/www/html directory
Comment 1 RHEL Program Management 2015-03-28 15:43:15 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 2 RHEL Program Management 2015-04-21 16:04:56 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 4 Megan Lewis 2015-06-29 05:51:33 UTC 
Hi Shannon, 

4.3.4. Importing Content to a Disconnected Satellite Server has been rewritten for the Satellite 6.1 Beta release and I believe the changes to the procedure have dealt with the issues outlined in this bug but wanted to confirm this with you? 

The new documentation is available here: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/User_Guide/sect-Red_Hat_Satellite-User_Guide-Using_Content_Management-Disconnected_Satellite.html#sect-Red_Hat_Satellite-User_Guide-Importing_Content_to_a_Disconnected_Satellite_Server

The new procedure instructs the user to unpack the isos into /var/www.html/sat-import/ (or another local directory that will be shared via httpd on the Satellite) and the note in step 6 now refers to "The Satellite is now acting as its own CDN with the files located in http://localhost" 

Thanks, 
Megan Lewis
Comment 5 Deon Ballard 2015-06-30 13:46:51 UTC 
Hey, Megan.

The incorrect location *is* /var/www.html/sat-import/

It should be /var/www/html/sat-import/ -- a forward slash, not a period between www and html.

I'm clearing the needinfo.
Comment 6 Deon Ballard 2015-06-30 21:14:41 UTC 
Oh, second thing... I am checking with Kearney about this, but the question is whether we need a separate directory or whether the apache config was fixed in the product. I'm guessing this is a doc fix, and (with the fixed directory name), the current 6.1 docs should address the initial problem. Unless this was fixed in the product and it's a moot point.
Comment 7 Rich Jerrido 2015-06-30 21:37:14 UTC 
we should use /var/www/html/pub/sat-import for this procedure. It is 

* Already existing and is used for other 'public' data on the Satellite AND
* requires no changes to the apache configuration.
Note You need to log in before you can comment on or make changes to this bug.