Hi Jon, The initial kickstart works fine for me as well. This seems to be a specific issue with Koan. The grub boot entry does appear, and the system boots using it, but instead of starting the installation process, it just boots into the existing OS. I am using the web interface to initiate the rebuild, so I'm not sure what parameters are passed on to Koan. Any suggestions how to troubleshoot this?
-Tomi On 9 April 2013 17:31, Jon Miller <[email protected]> wrote: > FYI, I have successfully kickstarted new FC18 clients from my Spacewalk > 1.9 server. What else do you have for your boot options? > > The closest I've see to what you are describing is when I have used koan > to initiate a rebuild of an existing FC18 client. When I only used the > "--replace-self" option, the grub boot entry still had the root=UUID=XXX > entry and when I removed that, it initiated a kickstart vs. a OS boot. Now > when I want to perform a re-install with koan I add the additional option > of "--no-copy-default" along with "--replace-self". > > -- Jon Miller > > > On Tue, Apr 9, 2013 at 1:32 AM, Tomi Salmi <[email protected]> wrote: > >> Hi, >> >> Re-provisioning a Fedora 18 system does not seem to work on Spacewalk >> 1.9. The system will reboot and boot with the kickstart option, but then it >> will proceed with loading the OS instead of the installer. >> >> Has anyone experienced the same? >> >> -Tomi >> >> _______________________________________________ >> 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
