Unattended Provisioning Troubleshooting » History » Version 7
Paul Armstrong, 03/02/2016 10:42 AM
| 1 | 1 | Corey Osman | h1. Unattended Provisioning Troubleshooting |
|---|---|---|---|
| 2 | |||
| 3 | 2 | Corey Osman | 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. |
| 4 | |||
| 5 | 1 | Corey Osman | h2. Host is stuck in PXEboot cycle after provisioning. |
| 6 | |||
| 7 | 4 | Christoph Witzany | h3. libvirt |
| 8 | |||
| 9 | 5 | Christoph Witzany | PXELinux is broken on some systems for versions >= 4.02. |
| 10 | |||
| 11 | 6 | Christoph Witzany | If new host fails to boot from the local hard disk, try to replace "LOCALBOOT 0" with "LOCALBOOT -1" in your PXE default template; |
| 12 | 5 | Christoph Witzany | If this does not help you can try "chain.c32 hd0,0" instead. |
| 13 | 4 | Christoph Witzany | |
| 14 | 1 | Corey Osman | h2. Host did not get the provision file |
| 15 | |||
| 16 | 3 | Florian Feldhaus | If your host can't get the provision file check your apache config. The foreman configuration should be in a file called <code>foreman.conf</code>. 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 <code>foreman.conf</code> should look similar to |
| 17 | |||
| 18 | <pre> |
||
| 19 | <VirtualHost *:80> |
||
| 20 | ServerName foreman.my.domain |
||
| 21 | ServerAlias foreman |
||
| 22 | DocumentRoot /usr/share/foreman/public |
||
| 23 | PassengerAppRoot /usr/share/foreman/ |
||
| 24 | RailsAutoDetect On |
||
| 25 | AddDefaultCharset UTF-8 |
||
| 26 | </VirtualHost> |
||
| 27 | |||
| 28 | <VirtualHost *:443> |
||
| 29 | ServerName foreman.my.domain |
||
| 30 | ServerAlias foreman |
||
| 31 | |||
| 32 | RailsAutoDetect On |
||
| 33 | DocumentRoot /usr/share/foreman/public |
||
| 34 | PassengerAppRoot /usr/share/foreman/ |
||
| 35 | |||
| 36 | # Use puppet certificates for SSL |
||
| 37 | |||
| 38 | SSLEngine On |
||
| 39 | SSLCertificateFile /var/lib/puppet/ssl/certs/mycert.pem |
||
| 40 | SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/mykey.pem |
||
| 41 | SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem |
||
| 42 | SSLCACertificateFile /var/lib/puppet/ssl/certs/ca.pem |
||
| 43 | SSLVerifyClient optional |
||
| 44 | SSLOptions +StdEnvVars |
||
| 45 | SSLVerifyDepth 3 |
||
| 46 | </VirtualHost> |
||
| 47 | </pre> |
||
| 48 | |||
| 49 | 7 | Paul Armstrong | |
| 50 | If your system failed to retrieve the kickstart file it may be due to the fact that the template build failed. |
||
| 51 | |||
| 52 | Use the spoof parameter by pointing your browser to a url similar to: |
||
| 53 | |||
| 54 | <pre> |
||
| 55 | http://foreman/unattended/provision?spoof=123.321.123.321 |
||
| 56 | </pre> |
||
| 57 | |||
| 58 | * 123.321.123.321 is the hosts IP Address (the one you want to build). |
||
| 59 | * usually you want to see the page source, the browser might display the file in html which will result in hard to read output. |
||
| 60 | * the completed template will be displayed or any errors that were encountered while the template was being built. |
||
| 61 | |||
| 62 | |||
| 63 | 1 | Corey Osman | h2. Some questions did not get answered by the provision file. |
| 64 | |||
| 65 | h2. Provision file is using the wrong installation media server. |