[PKG-Openstack-devel] OpenStack image for debian-testing

Steve McIntyre steve at einval.com
Tue May 10 12:53:38 UTC 2016

On Sun, May 08, 2016 at 02:38:41PM +0200, Thomas Goirand wrote:
>On 05/06/2016 09:56 AM, Jens Rosenboom wrote:
>> 2016-04-20 15:59 GMT+02:00 Thomas Goirand <zigo at debian.org>:
>>> On 04/20/2016 11:15 AM, Jens Rosenboom wrote:
>>>> The image at http://cdimage.debian.org/cdimage/openstack/testing/
>>>> doesn't seem to be working because due to the new interface naming,
>>>> the network will be named ensX but the system is still configured to
>>>> use eth0 only, at least that is how I interpret the console log.
>>>> Ubuntu seems to have seen similar issues, they first used a workaround
>>>> described in
>>>> https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1510345/comments/17
>>>> but with recent changes to cloud-init, their most recent xenial images
>>>> now run properly with the new naming scheme, see
>>>> http://paste.ubuntu.com/15943256/
>>>> Maybe you could generate an updated image with either the workaround
>>>> or after updating cloud-init.
>>> Hi,
>>> Thanks for your message, that's really useful.
>>> I have no time to work on a new version of cloud-init right now,
>>> however, I've added:
>>> biosdevname=0 net.ifnames=0
>>> to the kernel command line, until we can update cloud-init.
>>> Note that it will take 5 days for the openstack-debian-images package to
>>> migrate to testing, so we can expect a new, fixed, testing image in
>>> about a week and a half.
>> Should the new image be built automatically or does someone have to
>> trigger the build?
>It's normally generated together with the ISO images. Adding Steve as CC
>so he can tell.
>Steve, how come we don't have a new image? I thought it was generated
>weekly, and automatically? We'd need a fixed version with biosdevname=0
>net.ifnames=0 from the latest openstack-debian-images package...
>> It looks like there have been no new testing images for half a year now.
>I can seen images from 2nd of April:
>I'm not sure what the difference is between "current" and "testing"
>though. Maybe Steve can also tell...

Apologies, I disabled live image production a while ago due to
breakages and it looks like I disabled openstack too by mistake. I've
just fixed that now, and I've just triggered a build by hand.

Steve McIntyre, Cambridge, UK.                                steve at einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back

More information about the Openstack-devel mailing list