Bug 126630 - bootstrap script: faulty httpd proxy logic
Summary: bootstrap script: faulty httpd proxy logic
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Robin Norwood
QA Contact: Vlady Zlatkin
URL:
Whiteboard:
Depends On:
Blocks: 168311
TreeView+ depends on / blocked
 
Reported: 2004-06-23 22:51 UTC by Richard Keech
Modified: 2013-07-03 13:05 UTC (History)
2 users (show)

Fixed In Version: rhn401
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-10-20 23:22:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard Keech 2004-06-23 22:51:44 UTC
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:

Comment 1 Todd Warner 2004-06-29 21:23:55 UTC
Via an *HTTP* proxy, right?

Comment 2 Richard Keech 2004-06-30 00:30:19 UTC
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_"







Comment 3 Todd Warner 2004-07-28 15:02:12 UTC
Fixed in rhn350sat
At least in the commandline version of bootstrap stuff.
Double-checking the installer...

Comment 4 Todd Warner 2004-07-28 20:14:20 UTC
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.


Comment 5 Todd Warner 2004-07-28 22:32:31 UTC
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.

Comment 6 Robin Norwood 2004-07-29 21:33:25 UTC
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.

Comment 7 Max Spevack 2005-10-11 18:54:48 UTC
assigning QA contact based on our latest component ownership

Comment 8 Robin Norwood 2005-10-17 17:11:27 UTC
This bug was fixed long ago, but we should go ahead and qa it for appearences sake.

Comment 9 Robin Norwood 2005-10-17 17:26:31 UTC
Guessing rhn360

Comment 10 Vlady Zlatkin 2005-10-17 18:23:25 UTC
prod ready, enableProxy{,Auth} are correctly reset


Note You need to log in before you can comment on or make changes to this bug.