@Alex,
sorry for the slow reply.
Servicing 14.04 could still be done, but doing so would really require
some effort on the person wanting bug fixes in.
I had intended in comment 19 to point at my branch
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-
This bug was originally reported for Trusty, and my organization is
experiencing it with Trusty. I would note that 14.04 LTS still has two
years left in its support cycle. Do you plan on releasing a fix for
this?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Roy,
I'm attaching a suggested patch for trusty. I've not tested it, and my only
confidence in it is that the changes are down a very particular path (where
openstack provides network config).
If you're interested in pushing this a bit further, please grab that
patch and build and give it a
@Scott,
Could you please backport the fix to trusty image? Trusty image is still
widely used, and this still affects many until it is fixed in trusty
cloud image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is fixed in cloud-init 0.7.7
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use
@Scott
In which build this issue is fix?
In
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img
I have found same issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
marking fix-commited in cloud-init as revno 1225.
fix released in yakkety images and will make it back to xenial via sru.
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug
@smoser, hi any outlook on the fix for this? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in trusty
To manage notifications about this
@smoser, hi any outlook on the fix for this? Thanks.
--
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
That would require access to instance, how do you get into instance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in trusty
To manage
That would require access to instance, how do you get into instance?
--
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
@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
@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
Lots of people asking for workarounds, I figured I would post mine - it
involves deleting the eth0 file from /etc/network/interfaces.d prior to
using the image. So it goes a bit like this:
# Install qemu-utils
apt-get install qemu-utils
# Mount the Ubuntu cloud image
modprobe nbd max_part=63
Lots of people asking for workarounds, I figured I would post mine - it
involves deleting the eth0 file from /etc/network/interfaces.d prior to
using the image. So it goes a bit like this:
# Install qemu-utils
apt-get install qemu-utils
# Mount the Ubuntu cloud image
modprobe nbd max_part=63
I've tried 12.04 and have the same issue
--
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
I've tried 12.04 and have the same issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
i got same error on new instalation with Ubuntu 14.04.
Any ETA on a fix for cloud-init?
--
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
i got same error on new instalation with Ubuntu 14.04.
Any ETA on a fix for cloud-init?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in trusty
Is there any workaround for this bug ?
eth0 does not get its IP and the VM cannot be pinged or SSH'ed into.
cloud-init-nonet[13.74]: waiting 120 seconds for network device
cloud-init-nonet[133.74]: gave up waiting for a network device.
Cloud-init v. 0.7.5 running 'init' at Mon, 29 Dec 2014
Is there any workaround for this bug ?
eth0 does not get its IP and the VM cannot be pinged or SSH'ed into.
cloud-init-nonet[13.74]: waiting 120 seconds for network device
cloud-init-nonet[133.74]: gave up waiting for a network device.
Cloud-init v. 0.7.5 running 'init' at Mon, 29 Dec 2014
Any workaround or ETA please?
--
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
Any workaround or ETA please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
Any update on that issue? Is there anybody who can suggest a work around?
Thank you!
--
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
Any update on that issue? Is there anybody who can suggest a work around?
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in trusty
To
Any ETA on a fix for cloud-init?
--
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
Any ETA on a fix for cloud-init?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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:
** Changed in: cloud-init
Status: New = Confirmed
** Changed in: cloud-init
Importance: Undecided = High
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in: cloud-init
Your 'ask' comment at
https://ask.openstack.org/en/question/28297/cloud-init-nonet-waiting-and-fails/
/etc/network/interfaces shows:
# Injected by Nova on instance boot
If that entry was injected by nova, then there really isnt much or anything
cloud-init can do about this.
This is a good
Hi Scott,
You're correct, we use config drive in our implementation
(using_config_drive=True for nova-compute).
The template used by nova is located here:
https://github.com/openstack/nova/blob/master/nova/virt/interfaces.template
I also see your point that Nova could also implement a fix for
Adding the openstack nova bug for cross reference:
https://bugs.launchpad.net/nova/+bug/1319117
--
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
config drive != injection.
if nova injected the file (placed it in /etc/network/interfaces) then
there isn't anything I can do. Essentially, nova broke your image.
If nova placed the /etc/network/interfaces file on to a config drive,
and cloud-init read it and wrote /etc/network/interfaces then
** Changed in: cloud-init
Status: New = Confirmed
** Changed in: cloud-init
Importance: Undecided = High
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in: cloud-init
Your 'ask' comment at
https://ask.openstack.org/en/question/28297/cloud-init-nonet-waiting-and-fails/
/etc/network/interfaces shows:
# Injected by Nova on instance boot
If that entry was injected by nova, then there really isnt much or anything
cloud-init can do about this.
This is a good
Hi Scott,
You're correct, we use config drive in our implementation
(using_config_drive=True for nova-compute).
The template used by nova is located here:
https://github.com/openstack/nova/blob/master/nova/virt/interfaces.template
I also see your point that Nova could also implement a fix for
Adding the openstack nova bug for cross reference:
https://bugs.launchpad.net/nova/+bug/1319117
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315501
Title:
cloud-init does not use interfaces.d in
config drive != injection.
if nova injected the file (placed it in /etc/network/interfaces) then
there isn't anything I can do. Essentially, nova broke your image.
If nova placed the /etc/network/interfaces file on to a config drive,
and cloud-init read it and wrote /etc/network/interfaces then
37 matches
Mail list logo