From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: (Disclaimer: I've noticed this problem using the Whitebox RHEL rebuild, I haven't had chance to confirm it happens with proper RHEL, I imagine it does) I have a Squid proxy set up, with a tendency to retain RPMs for longer, which I use to fetch package updates through, as opposed to maintaining my own copies of the whole package trees. As part of my kickstart %post script, I create /etc/profile.d/proxy.* files containing the *_proxy environment variables so all shells get set correctly to use the proxy. Another thing I do within the %post script is to run 'up2date -f -u' to pull all of the latest updates in, and I ideally want to use the proxy for this step so prior to that I source the /etc/profile.d/proxy.sh to set the correct environment variables. What I found with some of my kickstart installs was that it was ignoring the proxy completely and downloading directly from each package repository. I traced the difference down to some kickstart scripts where I explicitly ran '/usr/sbin/up2date', these worked, but the ones where I just ran 'up2date' relying on the $PATH to do the dirty work, these didn't work. Using the Alt+F2 terminal within the installer environment I can replicate this whilst chrooted into /mnt/sysimage with the proxy environment variables set: Works: /usr/sbin/up2date or ./up2date with $PWD == /usr/sbin Doesn't work: up2date Once I've rebooted to the installation, up2date works correctly on all invocations, so it seems to be some strange interaction with the installation environment. Workaround is to explicitly state the full path to the up2date binary in the kickstart script. Version-Release number of selected component (if applicable): 4.1.16 How reproducible: Always Steps to Reproduce: 1. Within kickstart %post script, create environment variables pointing to Squid proxy 2. Run 'up2date -f -u' 3. Examine Squid proxy logs Actual Results: Logs show no client access from kickstart client. Expected Results: Logs should show kickstart client pulling Yum headers and RPM packages through proxy, (wherever possible). Additional info:
Blocking rhnupr4u4 and rhnupr3u8 to track the progress of the release
Moving bugs to the CanFix List
This bug did not make the code freeze and it will not be fiixed during this release cycle. Re-aligning bug to the next release
This bug did not make the code freeze. It will not be fixed in this releasee Reea ligning to the next one.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.