Deployment using findks via a Red Hat Proxy Server fails
Issue
- Deployment using findks via a RHN proxy fails
- We have worked out a solution for deploying RHEL systems using the Satellite
-
The solution works great but when using a proxy the solutions fails
- Systems are registered using cobbler. The MAC address is used to identify a system
-
The findks option is used to find the corresponding kickstart image in the cobbler database, eg.:
append initrd=initrd.img ks=http://<satellitehostname>/cblr/svc/op/findks kssendmac text noipv6
-
The kssendmac option provides the Satellite with a HTTP header 'X-RHN-Provisioning-MAC-0'.
- The solution described before does not work with a RHN proxy
- In our test lab we are trying to install a system that is reachable from a RHN proxy, but that is not reachable by the RHN Satellite.
-
The kickstart URL is modified to use the Proxy instead of the Satellite, eg.:
append initrd=initrd.img ks=http://<proxyserverhostname>/cblr/svc/op/findks kssendmac text noipv6
-
The problem with this solution is the kickstart file that is generated with the findks script
- It is identical to the file that is generated by the Satellite, which means the fresh installation tries to contact the Satellite instead to the Proxy
- Since the Satellite is not reachable the installation fails
Environment
- Red Hat Network Satellite and Proxy 5.5
- Cobbler
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.