Just tried it. No luck. It's strange. It's the hostname not resolving that is the problem. Reverse name lookup (IPv6) is what appears to be failing. When it says that it can't retrieve stage2.img, if I select OK, it allows me to edit the server and path. If I replace the servername with the IP address, it will continue just fine.
But when I used the IP address in the url setting --url http://10.50.1.20/var/distro-trees/CentOS5/ didn't work, but --url http://10.50.1.20/ks/dist/CentOS5/ did. On Mon, Oct 29, 2012 at 1:57 PM, Josh Preston <[email protected]>wrote: > Curious, > > All of my kickstart URLs look like: > > --url /ks/dist/ks-rhel-x86_64-server-5-5.7 > --url /ks/dist/ks-centos-x86_64-server-5-5.7 > > Have you tried just changing the /var to /ks ? > > Thanks! > > From: Mike Wilson <[email protected]> > Reply-To: spacewalk-list <[email protected]> > Date: Monday, October 29, 2012 2:10 PM > > To: spacewalk-list <[email protected]> > Subject: Re: [Spacewalk-list] Kickstart/DNS issue > > I was able to get it to work with an IP address rather than the DNS > name. Still frustrating that DNS wouldn't work, even though I've checked > and checked, and the spacewalk server is in DNS and WILL resolve. > > at Systems | Kickstart | Profiles | Kickstart Details | Advanced > Options, I changed the url option from > > --url /var/distro-trees/CentOS5 > > to > > --url http://10.xx.yy.zz/ks/dist/CentOS5/ > > That seemed to do the trick. > > On Mon, Oct 29, 2012 at 1:01 PM, Josh Preston <[email protected]>wrote: > >> Mike, >> >> The /etc/hosts file that I'm appending to in the PRE script is the >> install image's filesystem, not the system's end filesystem. It's the >> initial filesystem used immediately after booting, but before any packages >> or system configuration tasks. Changes made to that /etc/hosts are lost >> after the initial reboot. IIRC, this actually occurs after STAGE1 but >> before STAGE2. >> >> I have a couple meetings coming up, if I can get some free time, I'll >> take a quick look at our configuration. >> >> Thanks! >> >> From: Mike Wilson <[email protected]> >> Reply-To: spacewalk-list <[email protected]> >> Date: Monday, October 29, 2012 1:50 PM >> >> To: spacewalk-list <[email protected]> >> Subject: Re: [Spacewalk-list] Kickstart/DNS issue >> >> Josh, >> >> Thanks for the reply. I'm not having any luck with the pre-script >> though. It doesn't seem to be making a difference. I'm a little confused as >> to how/when the pre-scripts run. How do you write to /etc/hosts when the >> file system hasn't even been created yet? >> >> Is there some way within spacewalk to tell it to just use the spacewalk >> server's IP address instead of it's hostname? >> >> Also, I'm still very confused as to why it's trying to resolve reverse >> DNS for an IPv6 address. >> >> Mike >> >> On Mon, Oct 29, 2012 at 10:54 AM, Josh Preston <[email protected]>wrote: >> >>> Mike, >>> >>> As for #1: >>> >>> I've run into similar problems, and instead of figuring out what is >>> wrong, I instead opted to side step it by using a PRE script to ensure the >>> /etc/hosts file has the correct entry for the Satellite server: >>> >>> # Begin spacewalk/1/pre-configure-networking snippet >>> >>> #if $redhat_management_server == "my.satellite.fqdn.local" >>> echo "10.0.xx.yy $redhat_management_server" >> /etc/hosts >>> #else if $redhat_management_server == "my.satellite.proxy.fqdn.local" >>> echo "10.97.xx.yy $redhat_management_server" >> /etc/hosts >>> #else if $redhat_management_server == >>> "my.satellite.other.proxy.fqdn.local" >>> echo "172.16.xx.yy $redhat_management_server" >> /etc/hosts >>> #else >>> >>> # $redhat_management_server is not supported (ok); you better hope DNS >>> resolves correctly! >>> >>> #end if >>> >>> # End spacewalk/1/pre-configure-networking snippet >>> >>> >>> As for #2: >>> >>> I prefer to not register at the end of the installation (kickstart). >>> I instead prefer to register it to a specific activation key after the >>> system has been built. It's sort of like building a GOLD image (base >>> install) and then a second step of customizing it to a specific purpose. >>> >>> Thanks! >>> >>> >>> From: Mike Wilson <[email protected]> >>> Reply-To: spacewalk-list <[email protected]> >>> Date: Monday, October 29, 2012 11:15 AM >>> To: spacewalk-list <[email protected]> >>> Subject: Re: [Spacewalk-list] Kickstart/DNS issue >>> >>> I hope this isn't bad form, but I just wanted to give this a bump. >>> >>> On Fri, Oct 26, 2012 at 3:49 PM, Mike Wilson <[email protected]>wrote: >>> >>>> Is there some place in the kickstart profile to tell it NOT to use >>>> IPv6? >>>> >>>> >>>> On Fri, Oct 26, 2012 at 3:25 PM, Mike Wilson <[email protected]>wrote: >>>> >>>>> At the point in the install where it stops because it can't resolve >>>>> the spacewalk server's hostname, if I hit alt-F3, I can see more detail of >>>>> what is happening. >>>>> >>>>> It says reverse name lookup failed >>>>> starting to STEP_URL >>>>> URL_STAGE_MAIN - url is http://myswalkserver/ks/dist/CentOS5 >>>>> trying to mount CD device hda >>>>> trying to mount CD device scd0 >>>>> transferring http://myswalkserver//ks/dist/CentOS5/images/updates.imgto a >>>>> fd >>>>> we don't have reverse DNS for IPv6 yet >>>>> transferring >>>>> http://141swalk01//ks/dist/CentOS5/disc1/images/updates.img to a fd >>>>> ... more like that ("we don't have reverse DNS for IPv6 yet" appears a >>>>> few more times.) >>>>> >>>>> I'm not using IPv6. What gives? >>>>> >>>>> >>>>> On Fri, Oct 26, 2012 at 9:56 AM, Mike Wilson <[email protected]>wrote: >>>>> >>>>>> I just built a spacewalk server and I'm trying to use it to kickstart >>>>>> the build of another box. It mostly works fine, with 2 exceptions: >>>>>> >>>>>> 1. When the CentOS install starts, it says that it can't find the >>>>>> stage2.img file. It is trying to find it by the DNS name of my spacewalk >>>>>> server. It will let me edit where it's looking, and if I replace the >>>>>> server >>>>>> name with the server IP address, then it finds the file and the OS >>>>>> install >>>>>> completes. My spacewalk server provides DHCP, and valid DNS servers are >>>>>> included in the DHCP scope. After the install is complete and the newly >>>>>> built server boots up, it gets DHCP from the spacewalk server, >>>>>> /etc/resolv.conf is properly populated and I can successfully do an >>>>>> nslookup of the spacewalk server on it. So as far as I can tell, DHCP and >>>>>> DNS are working. Any suggestions? >>>>>> >>>>>> 2. When the kickstart completes, the newly built server is not >>>>>> registered in spacewalk. Shouldn't it be? Or do they always need to be >>>>>> registered manually? Or is it best to have it be registered through a >>>>>> post >>>>>> install script? I do have an activation key associated with the kickstart >>>>>> profile, and I've set up the tools child channel as outlined here: >>>>>> https://fedorahosted.org/spacewalk/wiki/HowToKickstartCobbler >>>>>> >>>>>> Any guidance is appreciated. >>>>>> >>>>> >>>>> >>>> >>> >>> _______________________________________________ >>> Spacewalk-list mailing list >>> [email protected] >>> https://www.redhat.com/mailman/listinfo/spacewalk-list >>> >> >> >> _______________________________________________ >> Spacewalk-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
