Description of problem: When a client is kickstarted thru a proxy, the url value in the kickstart should be populated with http://<proxy>/ty/blah. This makes the client fetch all packages directly from the satellite instead of thru the proxy. Version-Release number of selected component (if applicable): rhn-satellite-4.1.0-126 with -769 upgraded java & taskomatic How reproducible: Everytime Steps to Reproduce: 1. Setup a proxy on a satellite 2. Create a kickstart profile 3. Access the kickstart profile through the proxy (http://proxyhost/kickstart/ks/label/profile) Actual results: url has http://<satelllite_host>/ty/blah Expected results: url should have http://<proxy_host>/ty/blah
working on this now, will hopefully have a fix in the next couple hours.
TEST PLAN: See above :-)
available in: rhn-satellite-4.1.0-132-redhat-linux-as-i386-4.iso and on webqa, but you need to test this one on a satellite since we dont host kickstart trees in hosted.
fails_qa -- the URL says: http://rlx-3-04.rhndev.redhat.com/rhn/kickstart/ks-rhel-i386-as-4-u3 rlx-3-04.rhndev.redhat.com is the satellite test07.rhndev.redhat.com is the proxy
rhn-satellite-4.1.0-133-redhat-linux-as-i386-4-embedded-oracle.iso
This should show test07 instead of rlx-3-04: curl http://test07.rhndev.redhat.com/kickstart/ks/org/1x9356e892e806464270372c1cc6974318/label/ks-rhel-i386-as-4-u3 2>&1 |grep "url" url --url http://rlx-3-04.rhndev.redhat.com/rhn/kickstart/ks-rhel-i386-as-4-u3
Tested this on rlx-3-04 (that has patched jar file). The file it used had the following url: url --url http://test07.rhndev.redhat.com/ty/ytolIAXl you will want to update your rpms to the latest on this sat to re-test for real.
session that went through OK: https://rlx-3-04.rhndev.redhat.com/rhn/systems/details/kickstart/SessionStatus.do?sid=1000010004
Java packages are at: 4.1.0-776
Verified with 4.1.0-776.
moving to closed - currentrelease