Using the FQDN should be fine in our case. What do I need to go about changing and how do I change it to the fully qualified name? It seems like the SSL certs will give headaches if I do this because they are all signed for the short name (spacewalk server was set up "incorrectly" from the beginning it seems).
Thanks for your help! Greg On 2012-03-13 3:23 PM, "Miroslav Suchy" <msu...@redhat.com> wrote: >On 13.3.2012 15:38, Wojtak, Greg (Superfly) wrote: >> It does work directly from the spacewalk server. >> >> I probably should have been more clear in my previous email about what >>I'm >> perceiving the problem to be. >> >> The repo name in the URL is having the 'spacewalk' replaced as well. In >> this case, the repo is called spacewalk-client. I'm guessing that since >> my spacewalk server is simply called 'spacewalk', there's some sort of >> regex going on that replaces all occurrences of 'spacewalk' with my >>proxy >> name instead of just the domain portion of the URL. So >>'spacewalk-client' >> is becoming 'proxy.fqdn.tld-client' within the URL string. > >Aha. Indeed, we have in code which do the replacement something like: >s/fqdn-sw-server/fqdn-sw-proxy/ >And we do that replacement in whole kickstart file. Word by word. >And if your fqdn of spacewalk server is "install" or "selinux" or the >same name as your base channel name, then yes bad thing can happen. >Please do not do that. > >Write something which would replace only intended part of kickstart is >too hard. It is much easier to name your spacewalk at least >spacewalk.localdomain. > >Mirek > >_______________________________________________ >Spacewalk-list mailing list >Spacewalk-list@redhat.com >https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
