Puppet and Provisioning KVM VMs

Managed to figure this out, for others who have this issue, solution is below:

Open kickstart template and look at first few variables:

<%#
kind: provision
name: Kickstart default
model: ProvisioningTemplate
oses:

  • CentOS
  • Fedora
  • RedHat
    %>
    <%#
    This template accepts the following parameters:
  • lang: string (default=“en_US.UTF-8”)
  • selinux-mode: string (default=“enforcing”)
  • keyboard: string (default=“us”)
  • time-zone: string (default=“UTC”)
  • http-proxy: string (default="")
  • http-proxy-port: string (default="")
  • force-puppet: boolean (default=false)
  • enable-epel: boolean (default=true)
    - enable-puppetlabs-repo: boolean (default=false)
    - enable-puppetlabs-pc1-repo: boolean (default=false)
    - enable-puppetlabs-puppet5-repo: boolean (default=false)
  • salt_master: string (default=undef)
  • ntp-server: string (default=“0.fedora.pool.ntp.org”)
  • bootloader-append: string (default=“nofb quiet splash=quiet”)
  • disable-firewall: boolean (default=false)
  • package_upgrade: boolean (default=true)
  • disable-uek: boolean (default=false)

The 3 puppet repos are false by default. Choose the repo you want to enable for the puppet agents to download from (for me it was enable-puppetlabs-pc1-repo)

Then goto Global Parameter, create a new parameter and name it as per the template (eg. enable-puppetlabs-pc1-repo). Then in value enter true

New machine now provisions with puppet-agent 4.10.

Cheers