Bug #12480
closed
Error when trying to provision a new VM via network based install
Added by Anthony Lapenna about 9 years ago.
Updated over 7 years ago.
Description
Hello,
This error appears occasionally when trying to provision a VM on a VMWARE provider via a network based install (see image in attachment).
This error can be viewed on the virtual machine itself by accessing it via the vSphere client console.
When trying to check the URL it returns a 404 code.
$ curl -w %{http_code} -s -o /dev/null 'http://foreman.wit.prod:80/unattended/finish?token=09077d68-1c31-439f-8265-2bc8071a6e00'
404
Note that this issue does not block the provisioning, you can just press enter to continue and the installation will proceed.
Files
- Status changed from New to Need more information
Could you provide the logs from Foreman (/var/log/foreman/production.log) during the request from the installation? This should show where the problem is - e.g. it doesn't recognise the host, a template error etc. Although it may not stop installation, it probably prevents the finish script from running.
I've attached the logs related to the installation request.
The log shows an image build, not a network install. It also doesn't show the finish template request, so either, a) the log's wrong, or b) the request isn't making it to Foreman (some network, DNS etc issue).
My bad, it seems that the VM has been built via image, deleted and then rebuilt via network.
Logs attached.
Do you have any later logs? You should see requests for:
/unattended/provision - the main preseed, which must be working to have got it that far
/unattended/finish - the finish script, which appears to be failing
- Status changed from Need more information to Feedback
The log shows multiple requests to /finish, the first of which is working fine (2015-11-13T13:41:10). The ones later (2015-11-13T13:46:42) are probably you testing, but the server was built by that stage so they returned 404.
I think the screenshot is probably instead saying that something inside your finish script failed. Have a look at the template and the preview and try to debug it - perhaps a command is failing. You can always add some logging to it, e.g.
(
... commands
) 2>&1 | tee /root/install.post.log
and check the log on the server after installation.
Ok, I'll try to debug my finish script.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Anonymous