[Bug 1315501] Re: cloud-init does not use interfaces.d in trusty

[David Moreau Simard]

@Bobby

My workaround is applied to the image the instance is spawned with. You
must modify the image, upload that modified image and you will be able
to successfully boot VMs without this issue.

If you do not have access to do that, the only other way I would see
would be to spawn a VM using the image with this problem but pass user-
data to cloud-init to grant you console access, a bit like this:

#cloud-config
users:
  - name: root
    lock-passwd: false

chpasswd:
  list: |
    root:root
  expire: false

This will allow you to login as root (with password 'root') in the VM
console where you'll be able to either delete the extra eth0 file or
diagnose the problem from there.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1315501

Title:
  cloud-init does not use interfaces.d in trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1315501/+subscriptions