Red Hat Bugzilla – Bug 126154
Proxy doesn't have bootstrap files
Last modified: 2007-10-23 21:37:51 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040614 Firefox/0.8 Description of problem: When a proxy is created, the bootstrap directory is not created on proxy. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Build AS 2.1 machine according to Proxy Guide 2. Install Proxy according to Proxy Guide 3. No pub/bootstrap exists for registration Actual Results: There is no /var/www/html/pub/bootstrap directory with files. The files exist on Satellite, but there is no way for a client who can not talk to Satellite to get the files. Expected Results: During an install the pub/bootstrap should be created and populated. A script to sync between Proxy and Satellite *might* make sense Additional info:
Adding the bootstrap script generation facilities to RHN Proxy has been on my TODO list for some time now. It's a matter of finding the time. You can easily scp or rsync the necessary scripts to the pub directory of the RHN Proxy and hand modify the scripts. I know this is not ideal, but it is also not overly hard. It works fine for the short-term.
Sounds good. I wanted to make sure that someone else thought it was a good idea and was on a TODO list. BTW, that is what I did-- setup some foo to check the files and pull and modify as required.
Done for RHN Proxy 3.5.0, which is not being released, so it should be in the next version that is released... whatever that is. :) Test plan start point (for QA guys): ------------------------------------ o rhn-bootstrap tool tests fine on an RHN Proxy (see test plans for RHN Satellite that has the same tool). o webUI interface (on RHN sat or hosted) still in flux... that will be another bug that gets a seperate test plan.
Docs note: o docs need to note that if a customer is running an RHN Proxy below an RHN Satellite, that creating bootstrap scripts from the RHN Satellite and scping or rsync them to the RHN Proxy may be the easiest way to generate them... similar to server-side SSL key-pairs. Need to hash this out.
ON_QA -> ASSIGNED Tool is being modified... and we need to reverify this bug. Blocking bug changed from rhn350proxy --> bug 132275
Done for 3.6.0 Now to make it work! :) TEST PLAN: ---------- o follow docs to generate bootstrap scripts (RHEL 2.1 and RHEL 3 clients) on an RHN Proxy o test that you can use scripts against RHN Proxy DOCS: ----- o need to reference bootstrap stuff in proxy docs. Not sure where they are in the satellite. I would have to look it up.
QA push. {ON_DEV,QA_READY} --> ON_QA
see bug #134592
once again this is another bug to test the bootstrap tool *** This bug has been marked as a duplicate of 132275 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.