Bug 1259394 - Configuring Proxy Precaching
Summary: Configuring Proxy Precaching
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Proxy Installation Guide
Version: 570
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Dan Macpherson
QA Contact: Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks: sat570-triage
TreeView+ depends on / blocked
 
Reported: 2015-09-02 13:59 UTC by Fotios Tsiadimos
Modified: 2019-08-15 05:17 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description Fotios Tsiadimos 2015-09-02 13:59:17 UTC
Description of problem:
The documentation says that the rsync for the pre-cache for RHN-PROXY servers should be as below but also says the pre-cache option is only for custom channels not the RHEL channels:


rsync from sat:/var/satellite/redhat/*/  to proxy:/var/spool/rhn-proxy/rhn


Version-Release number of selected component (if applicable):
Satellite 5.7 or 5.6

How reproducible:

In the Official Documentation of Proxy the first line in the below chapter: 

4.2. Configuring Proxy Precaching
Your Proxy server can precache or mirror custom RPM files.  

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html/Proxy_Installation_Guide/sect-Configuring_Proxy_Precaching.html

At the end of the Doc the example show to sync all the channels:

crontab -e
1 3 * * * /usr/bin/rsync -r user.com:/var/satellite/redhat/*/ /var/spool/rhn-proxy/rhn

Comment 2 Dan Macpherson 2015-09-09 02:09:18 UTC
So if I understand correctly, the issue is that we initially state it's for precaching custom channels when really it's for precaching all channels. Is this just a case of removing all references to "custom" in this section?

Comment 5 Dan Macpherson 2016-07-12 02:40:07 UTC
Closing BZ due to inactivity. However, feel free to reopen if further changes are required.


Note You need to log in before you can comment on or make changes to this bug.