Description of problem: The bootstrap script fails where the client system was previously connected to RHN via a proxy. Version-Release number of selected component (if applicable): RHN Satellite 3.2 (build 12 iso). Actual results: I see that the bootstrap script fails to allow the client to register to the satellite because "enableProxy" in /etc/sysconfig/rhn/up2date has not been reset. Expected results: Bootstrap script should reset "enableProxy" value, thereby allow the client system to connect to the proxy. Additional info:
Via an *HTTP* proxy, right?
Yes, the previous client connection was via a regular web proxy cache. And "Bootstrap script should reset enableProxy value, thereby allow the client system to connect to the _proxy_." should have read "Bootstrap script should reset enableProxy value, thereby allow the client system to connect to the _satellite_"
Fixed in rhn350sat At least in the commandline version of bootstrap stuff. Double-checking the installer...
Ok... changed again. With the new rhn-bootstrap utility you *must* explicitely state your HTTP proxy values: "" means OFF "XXX:PORT" means on. The same goes for username and password "" means off and "USERNAME" means on. --overrides --client-version and --script have been added for more control at the commandline. So... rhn-bootstrap --http-proxy="" --client-version=2 --overrides=/var/www/html/pub/bootstrap/client-config-overrides-RHEL2.1.txt --script=/var/www/html/pub/bootstrap/boostrap-RHEL2.1.sh rhn-bootstrap --http-proxy="" --client-version=4 --overrides=/var/www/html/pub/bootstrap/client-config-overrides-RHEL3.txt --script=/var/www/html/pub/bootstrap/boostrap-RHEL3.sh ...are good examples of how to use this. Punting to rnorwood to finish up the installer portion of this.
Additional note: --http-proxy has to be set to either "" or "HOSTNAME:PORT" "" == http proxy is disabled If it is set to something, --http-proxy-username has to be set to "" or "SOME_USERNAME" "" == auth is disabled If that is set to something, --http-proxy-password has to be set to "SOME_PASSWORD" If you think about it for a second it all makes sense.
Ok - now we are calling rhn-bootstrap properly. Test plan: Run the satellite installer, and ensure that the proper bootstrap files are created: /var/www/html/pub/bootstrap/boostrap-RHEL2.1.sh /var/www/html/pub/bootstrap/boostrap-RHEL3.sh And ensure that they contain the correct settings for the options you specified during the install.
assigning QA contact based on our latest component ownership
This bug was fixed long ago, but we should go ahead and qa it for appearences sake.
Guessing rhn360
prod ready, enableProxy{,Auth} are correctly reset