Ubuntu
curtin package

  1. Bug #1717176
  2. Comment #8

Comment 8 for bug 1717176

Revision history for this message
Christian Ehrhardt  (paelzer) wrote : Re: Fail to install wichita box

Here the console log while commisioning.
It ends in http issues.

The IP is correct the path seems to miss something '//' maybe ?
I don't know from what this is generated but 2012-03-01 seems old?

This seems to be after some install activity:

Cloud-init v. 0.7.5 running 'modules:final' at Thu, 14 Sep 2017 07:05:23 +0000. Up 57.45 seconds.
Ign http://ports.ubuntu.com trusty InRelease
[...] (apt)
Setting up sshpass (1.05-1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.13) ...
Processing triggers for ureadahead (0.100.0-16) ...
modprobe: ERROR: could not insert 'ipmi_si': No such device
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 1.: HTTP Error 400: BAD REQUEST
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 1.: HTTP Error 400: BAD REQUEST
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 2.: HTTP Error 400: BAD REQUEST
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 4.: HTTP Error 400: BAD REQUEST
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 8.: HTTP Error 400: BAD REQUEST
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 16.: HTTP Error 400: BAD REQUEST
request to http://10.245.71.3/MAAS/metadata//2012-03-01/ failed. sleeping 32.: HTTP Error 400: BAD REQUEST
FAIL: HTTP error [400]