In satellite 5.2 in prior you could bare metal kickstart a machine through a proxy by simply replacing the hostname in a kickstart URL with the hostname of the proxy. In satellite 5.3 you cannot do this. Even if you hack it to proxy the kickstart file, none of the URLs within the kickstart file ( distro url, registration url) are modified to go through the proxy.
moving to sat530-ks, gotta make sure this works.
we search-replace the cobbler host in the KS file. Simple way to test is to hit the baremetal URL: Satellite: http://somesat.rhndev.redhat.com/ks/cfg/org/1/label/mmccune-rhel5-i386 Proxy: http://someproxy.rhndev.redhat.com/ks/cfg/org/1/label/mmccune-rhel5-i386 you should not see any instances of somesat.rhndev.redhat.com if you download that kickstart file through the proxy.
ON_QA
VERIFIED. all url are replaced. I tried to do KS and it indeed use proxy. In the middle I had to stop due to bug in vmware so I did not finish whole KS, but it seems unnecessary.
I kickstarted a xen guest using a bare metal kickstart profile through proxy. Guest was kickstarted without any issues. Moving to release_pending.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html