Unattended Provisioning Troubleshooting » History » Version 6

« Previous - Version 6/7 (diff) - Next » - Current version
Christoph Witzany, 01/08/2013 08:11 AM

Unattended Provisioning Troubleshooting

Below are some topics and troubleshooting steps that you may encounter while using the unattended provisioning. Please add topics or provide answers if you can.

Host is stuck in PXEboot cycle after provisioning.


PXELinux is broken on some systems for versions >= 4.02.

If new host fails to boot from the local hard disk, try to replace "LOCALBOOT 0" with "LOCALBOOT -1" in your PXE default template;
If this does not help you can try "chain.c32 hd0,0" instead.

Host did not get the provision file

If your host can't get the provision file check your apache config. The foreman configuration should be in a file called foreman.conf. There you have the vHost configuration for HTTP and HTTPS access. If you have multiple interfaces in your foreman server, you must make sure that the right IP address under which the host tries to access the foreman server is configured here. You may also configure apache to listen on all interfaces by using the * wildcard. Your foreman.conf should look similar to

<VirtualHost *:80>
  ServerAlias foreman
  DocumentRoot /usr/share/foreman/public
  PassengerAppRoot /usr/share/foreman/
  RailsAutoDetect On
  AddDefaultCharset UTF-8

<VirtualHost *:443>
  ServerAlias foreman

  RailsAutoDetect On
  DocumentRoot /usr/share/foreman/public
  PassengerAppRoot /usr/share/foreman/

  # Use puppet certificates for SSL

  SSLEngine On
  SSLCertificateFile      /var/lib/puppet/ssl/certs/mycert.pem
  SSLCertificateKeyFile   /var/lib/puppet/ssl/private_keys/mykey.pem
  SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem
  SSLCACertificateFile    /var/lib/puppet/ssl/certs/ca.pem
  SSLVerifyClient         optional
  SSLOptions              +StdEnvVars
  SSLVerifyDepth          3

Some questions did not get answered by the provision file.

Provision file is using the wrong installation media server.