** Project changed: ubuntu-on-ec2 => cloud-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device
this is fix-released from cloud-init perspective in xenial.
If you disagree, please state why and open the bug. cloud-init now renders
.rules files and configures ENI per the datasource's provided network config or
a fallback network config.
** No longer affects: cloud-init
** Changed in:
this is fix-released from cloud-init perspective in xenial.
If you disagree, please state why and open the bug. cloud-init now renders
.rules files and configures ENI per the datasource's provided network config or
a fallback network config.
** No longer affects: cloud-init
** Changed in:
Looks like I was premature in my last reply.
ami-bfb5ead5 just came up. I'll have to double check this bug report with one
of our customers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
OK it looks like the bug was fixed for the hvm:ebs-ssd (General Purpose
SSD) AMI builds and not hvm:ebs (standard/magnetic EBS).
For example, in ubuntu-wily-15.10-amd64-server-20160105.1 for us-east-1:
* ami-bfb5ead5 ( hvm:ebs ) - FAILS
* ami-15b7e87f ( hvm:ebs-ssd ) - WORKS
for enhanced
Looks like I was premature in my last reply.
ami-bfb5ead5 just came up. I'll have to double check this bug report with one
of our customers.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
OK it looks like the bug was fixed for the hvm:ebs-ssd (General Purpose
SSD) AMI builds and not hvm:ebs (standard/magnetic EBS).
For example, in ubuntu-wily-15.10-amd64-server-20160105.1 for us-east-1:
* ami-bfb5ead5 ( hvm:ebs ) - FAILS
* ami-15b7e87f ( hvm:ebs-ssd ) - WORKS
for enhanced
Do we have any updates for fixing these AMIs for instance types that
have enhanced networking enabled?
--
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/1510345
Title:
[SRU] Cloud
Do we have any updates for fixing these AMIs for instance types that
have enhanced networking enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring
Some of the newest Amazon EC2 Published AMIs at [1], for example,
ubuntu-wily-15.10-amd64-server-20151219 AMIs: ami-38796759 (us-west-2) &
ami-94683ffe (us-east-1) only successfully boot for instance types that
don't have enhanced networking enabled
Some of the newest Amazon EC2 Published AMIs at [1], for example,
ubuntu-wily-15.10-amd64-server-20151219 AMIs: ami-38796759 (us-west-2) &
ami-94683ffe (us-east-1) only successfully boot for instance types that
don't have enhanced networking enabled
Pardon me if I'm missing something, but I just launched a new c4.xlarge
instance using AMI ami-47723b2d from https://cloud-
images.ubuntu.com/wily/20151209/ .
The result was identical to Lawrence Rowe's original report. Same log
output, same interface names, no eth0. This bug report indicates
Pardon me if I'm missing something, but I just launched a new c4.xlarge
instance using AMI ami-47723b2d from https://cloud-
images.ubuntu.com/wily/20151209/ .
The result was identical to Lawrence Rowe's original report. Same log
output, same interface names, no eth0. This bug report indicates
Regressed; reported at https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/1525015
--
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/1510345
Title:
[SRU] Cloud Images do
Regressed; reported at https://bugs.launchpad.net/ubuntu/+source/livecd-
rootfs/+bug/1525015
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are
** Tags added: rls-x-incoming
--
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/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device
** Tags added: rls-x-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device naming rules
To
This bug was fixed in the package livecd-rootfs - 2.349.1
---
livecd-rootfs (2.349.1) wily; urgency=medium
* cloud-images: revert to old device naming (LP: #1510345).
-- Ben Howard Thu, 29 Oct 2015 11:29:01 -0500
** Changed in: livecd-rootfs (Ubuntu
** Tags added: patch
--
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/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device naming
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device naming rules
To manage
This bug was fixed in the package livecd-rootfs - 2.349.1
---
livecd-rootfs (2.349.1) wily; urgency=medium
* cloud-images: revert to old device naming (LP: #1510345).
-- Ben Howard Thu, 29 Oct 2015 11:29:01 -0500
** Changed in: livecd-rootfs (Ubuntu
Verified. Good for release.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up
Setting net.ifnames=0 in livecd-rootfs was a quick hack for wily, but
this is really inconvenient. This means that the cloud images now stop
being usable for non-cloud workloads (or even for cloud workloads with
multiple NICs).
The proper fix would be for cloud-init to generate a network config
Setting net.ifnames=0 in livecd-rootfs was a quick hack for wily, but
this is really inconvenient. This means that the cloud images now stop
being usable for non-cloud workloads (or even for cloud workloads with
multiple NICs).
The proper fix would be for cloud-init to generate a network config
Hello Laurence, or anyone else affected,
Accepted livecd-rootfs into wily-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.349.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Dailies for Ubuntu Cloud Images have finished publishing at [1].
Confirmed that c4.xlarge instances on AWS get networking, tested on GCE
and Azure builds as well. Automated testing preliminary results looks
promising, so I've started the promotion process. Pending the results of
testing (eta ~2
** Changed in: livecd-rootfs (Ubuntu Wily)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu Wily)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New 15.10 images have been released to [1]. I've updated the AWS forum
as well.
The SRU aspect is bringing the fix into livecd-rootfs which is used to
build the images; this package is not in the image itself. For the time
being Cloud Images are being built using a PPA until the fix lands in
30 matches
Mail list logo