<div dir="ltr">Aloha there,<div><br></div><div>The point of kickstart is so you can manually make it do exaclty what you need to get a standard build without having the faff of extra scripts to run at the end :)</div><div><br></div><div>1) I use a post scrip to to move the files out of yum.repos.d so that they are ignored, I prefer moving to deleting incase i screw something up in spacewalk :)</div><div><br></div><div>2) You need to import the GPG key in the kickstart, if you have used the space command tool to make the repos I think the GPG key is imported to spacewalk automattically, if not check the gpg keys, then if they are there and correct in the actual kickstart make sure they are checked to be imported during build time. This should solve it</div><div><br></div><div>3) To be honest i would recommend using DHCP, even if its just in the build environment,</div><div><br></div><div>4) To use snippets paste the macro in the post script, the macro is the $ ones. Then at the bottom of the script editing page there is a checkbox that syas something along the lines of enable templating. Once that is clicked when you view the "raw" kickstart you will see the macro replaced with the snippet. I tend to keep all actions in snippets rather than scripts as then they are centra for all builds so im only changing one thing rather than 6</div><div><br></div><div>5) You should try and make them generic, what is it thats differnt about them? If its the network config then dhcp ;), the passwords I set default "weak" ones then modify the MOTD of the box to add a TODO checklist before the box is pushed into production, on there is change + record the disk encyption and root passwords. My kickstarts also ask for user input when needed :), never got that part to work in centos 7 though</div><div><br></div><div>6) i had the same "problem" (Its not really a problem just a wierd way of doing it), in the kickstart theres a packages section, you just need to add that and some others to there, however i dont have my notes at the moment so i couldnt say what they are till monday :)</div><div><br></div><div>On a side note would it be usefull for you to have a Wiki style page to follow going through the options and such? (not sure if there is one) i could write on up for the Main spacewalk site (and yoink it for my website ;D) If it would help :), </div></div><div class="gmail_extra"><br><div class="gmail_quote">On 22 May 2015 at 17:08, Will Beldman <span dir="ltr"><<a href="mailto:wbeldma@uwo.ca" target="_blank">wbeldma@uwo.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Everyone,<br> <br> I'm very new to both Spacewalk (using v2.2) and Kickstart. I'm trying to<br> stumble through my first CentOS 7 kickstart. I'd like to avoid manual<br> customizations as much as I can so I have a few questions:<br> <br> 1. I've got as far as successfully completing a kickstart and it automatically<br> registers the host in Spacewalk. At this point, I would like the machine to<br> disable any locally configured repos and depend on Spacewalk only. Should I<br> create my own post script to do this?<br> <br> 2. So I manually disable locally configured repos and it is using Spacewalk<br> only, but I cannot run updates locally. yum update gives the standard GPG key<br> error message:<br> ==================<br> You have enabled checking of packages via GPG keys. This is a good<br> thing...<br> ...<br> rpm --import public.gpg.key<br> ...<br> Problem repository: centos-7-64bit<br> ==================<br> I see from the generated kickstart file, in the post script, the Spacewalk<br> cert is being dropped in /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT but no rpm --<br> import line for it. There is a line to do:<br> rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release<br> But since this is CentOS, this doesn't do anything.<br> Is this normal? Should I also add an rpm --import line in another customized<br> post script?<br> <br> 3. We do not use DHCP in our environment so I am kickstarting via static IP<br> and I need to set kickstart to use static as well. I have manually updated the<br> network advanced option to:<br> --bootproto=static --ip=$IP --netmask=$NM --gateway=$GW --hostname=$HN --<br> nameserver=$NS1 --nameserver=$NS2 --nameserver=$NS3<br> and I added variables to match my specific host. First of all, it looks like<br> my nameservers are being ignored. My kickstarted machine is using the<br> nameserver I specified at boot time when I kickstarted it and not the three I<br> set here. Second, does this approach make sense? I see it listed as an example<br> in some documentation (<a href="https://access.redhat.com/documentation/en-US/Red_Hat_Network_Satellite/5.3/html/Reference_Guide/s1-cobbler-templates.html#s2-cobbler-templates-usage" target="_blank">https://access.redhat.com/documentation/en-US/Red_Hat_Network_Satellite/5.3/html/Reference_Guide/s1-cobbler-templates.html#s2-cobbler-templates-usage</a>), but I also see that are snippets<br> listed in my Spacewalk server that I could take advantage of?:<br> network_config $SNIPPET('network_config')<br> post_install_network_config $SNIPPET('post_install_network_config')<br> pre_install_network_config $SNIPPET('pre_install_network_config')<br> Should I configure the network settings in the kickstart config or can I be<br> prompted for that in the installer? Or can I get the machine to assume the<br> boot parameters I supplied for the network configuration?<br> <br> 4. On that subject, how do I use snippets in kickstart through Spacewalk?<br> There are a handful there and a bunch I can find online. Spacewalk says: "TIP:<br> Copy and paste the snippet macro into your kickstart profiles to make the full<br> snippet appear in that kickstart profile."<br> Okay, where? In the advanced options? Do I download my automatically generated<br> kickstart file, modify it, and re-upload it?<br> <br> 5. Is it common to have one kickstart config per machine? Every time I want to<br> spin up a new machine, should I clone a "base" kickstart profile and modify<br> the settings appropriately to make it machine specific? Or is it possible to<br> template a kickstart profile enough to have exactly one to work from. In the<br> end, at least for now, I would be looking for every kickstarted machine to be<br> identical except for network configuration and root password.<br> <br> 6. I checked off "Enable Spacewalk Configuration Management" and "Enable<br> Spacewalk Remote Commands" but rhncfg-actions does not get installed so this<br> cannot be working. I can manually add the package to the list of software to<br> be installed but this should not be necessary.<br> <br> Help on any of these questions would be greatly appreciated.<br> <br> _______________________________________________<br> Spacewalk-list mailing list<br> <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br> </blockquote></div><br></div>