Red Hat Bugzilla – Bug 123138
explain how we make synced trees available
Last modified: 2009-08-19 23:05:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124
Description of problem:
Section '18.104.22.168 Distributions' should really explain about the
availability of synced channels at
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. read docs (specifically section '22.214.171.124 Distributions')
2. wonder if you need to make a fully exploded tree of, say
rhel-i386-es-3-u1 available on your Satellite
3. read the one sentence about Sat in that paragrah
Actual Results: need more input ;-)
Expected Results: a few lines explaining that synced trees are made
Satellite users should note that channels, they imported into their
Satellite with satellite-sync, are made available on the fly. i.e. ,
if you have synced 'rhel-i386-es-3' and the current release is
rhel-i386-es-3-u1, there is absolutely no need to make an installation
tree available. The Satellite will make the RPMs available on the fly.
So when you are kickstarting a client, the only thing to do is to
select the correct distribution in the details of your kickstart profile.
Please note that these trees are only guaranteed to be available to
clients that kickstart through the RHN Satellite. While you may be
able to access the files from a non-kickstarting client, this
functionality is not supported and may be removed at any time in the
Wow, this was never really conveyed to me, Patrick. Excellent input.
Keep drafting such descriptive text and you're going to put me out o'
business. And I ain't complaining.
Aligning to the newly created 3.4 documentation tracking bug and
setting to customer facing=yes. Will work to incorporate this
information into the docs this release. Thanks again.
Alright, I've added Patrick's text almost verbatim. Good stuff.
Setting to ON_DEV.
Forgot to mention, I added this as an Important note for emphasis.