32bit AMI issues (unofficial AMI)

milanisko k vetrisko at gmail.com
Thu Oct 30 16:51:29 UTC 2014


looking at [2], lines 605--612, there's just the loop-back device therefore
cloud-init fails to fetch instance metadata.
Not sure why there's no other NIC device, though...

--
milan

2014-10-30 16:55 GMT+01:00 Dusty Mabe <dusty at dustymabe.com>:

>
> Last night I created some AMIs for roshi to test using the procedure at
> [1].
> I then booted the x86_64 AMI (ami-145fdd7c) and it seemed fine. The i386
> AMI
> (ami-de6be9b6) had issues booting (see [2] for full log). Has anyone else
> seen this before?
>
> [[32m  OK  [0m] Started System Logging Service.
> [[32m  OK  [0m] Started OpenSSH Server Key Generation.
> [   17.320770] cloud-init[332]: Cloud-init v. 0.7.5 running 'init-local'
> at Thu, 30 Oct 2014 04:30:06 +0000. Up 17.22 seconds.
> [[32m  OK  [0m] Started Initial cloud-init job (pre-networking).
> [[1;31mFAILED[0m] Failed to start LSB: Bring up/down networking.
> See "systemctl status network.service" for details.
>
> Thanks,
> Dusty
>
> [1] - https://gist.github.com/dustymabe/3d53cfe6b9ae32c5e2fb
> [2] - http://ur1.ca/im3op
> _______________________________________________
> cloud mailing list
> cloud at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/cloud
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/cloud/attachments/20141030/4270c454/attachment.html>


More information about the cloud mailing list