[Spacewalk-list] How to test Spacewalk Proxy

[Jon Miller]

Just wanted to report back that all is working fine with my Proxy. Turns out
the person that imaged my proxy machine, typo'ed the local /etc/hosts
file. We realized this after seeing the hitting the IP directly would work to
retrieve the kickstart file fine.

One more quick question. It appears that I'm going to need a separate proxy
server for each organization that requires a DMZ presence. Is that the
correct conclusion or is there a way to re-use the same proxy for multiple
organizations? 

Thanks,
Jon Miller

michael.mraka at redhat.com writes:

> Jon Miller wrote:
> % > % The webpage eventually returns and provides the following error:
> % > % XML Parsing Error: no element found
> % > % Location: http://spacewalk-dmz.example.com/ks/cfg/org/3/label/base
> % > % Line Number 1, Column 1:
> % > % 
> % > % I have verified that my firewall is allowing ports 80, 443, 5269 via
> % > % some telnet tests.
> % > % 
> % > % Here is what squid is seeing via it's access.log:
> % > % 1373062140.709 120023 127.0.0.1 TCP_MISS/000 0 GET
> % > % http://spacewalk-dmz.example.com/ks/cfg/org/3/label/base -
> % > % DIRECT/spacewalk-dmz.example.com -
> % > % 
> % > % I'm not that familiar with squid but that almost reads to me like
> % > % Squid is trying to retrieve the resource from the same dmz machine vs.
> % > % my internal Spacewalk server. Should I be propagating the same DNS
> % > % name in the dmz for my proxy as what I have internally?
> % >
> % > Hi Jon,
> % >
> % > the easiest way to test spacewlak proxy is to register a client to the
> % > proxy.
> % >
> % > As for DNS - if you can see proxy registered in spacewalk's webUI and it
> % > can update itself from the spacewalk then DNS setup is OK.
> % I had originally registered my DMZ machine with the base organization
> % and have since re-registered it with another active org and re-ran the
> % configure-proxy.sh script. That completed and I now see the DMZ proxy
> % machine listed in my proxy section with the internal Spacewalk UI. 
> % 
> % I have returned to my test of using a known, working kickstart URL to test the
> % functionality of the DMZ and I'm still getting the XML error returned to
> % the browser after a timeout period.
> % 
> % Does the proxy actually support imaging machines directly from it as I
> % would from the internal Spacewalk server?
>
> Yes, kickstarting via proxy should work, otherwise it's a bug.
>
> If http://spacewalk-dmz.example.com/ks/cfg/org/3/label/base is an URL of
> kickstart file on spacewalk server then 
> http://spacewalk-proxy.example.com/ks/cfg/org/3/label/base should return
> the same text file (with all references to spacewalk-dmz.example.com replaced
> by references to spacewalk-proxy.example.com).
>
>
> Regards,
>
> --
> Michael Mráka
> Satellite Engineering, Red Hat
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list