DataSourceOpenNebula.py doesn't configure network

Bug #1719157 reported by Akihiko Ota on 2017-09-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Unassigned

Bug Description

I am using OpenNebula 5.4 cloud environment.
I tried to create Ubuntu 16.04 server instance from image that is installed cloud-init 0.7.9-233-ge586fe35-0ubuntu1~16.04.1.
The configuration of HOSTNAME and SSH_PUBLIC_KEY works fine, but network configration doesn't work and fallback to dhcp.

It seems that DataSourceOpenNebula.py creates the soruce of network configrations from context.sh, but it has no appropriate network_config property. So cloud-init doesn't get network configuration.

I wrote attached patch. It works fine on my environment.

my cloud provider:
   OpenNebula 5.4

instance's cloud-init:
   $ dpkg-query -W -f='${Version}' cloud-init
   0.7.9-233-ge586fe35-0ubuntu1~16.04.1

   This instance's image is downloaded from Ubuntu Cloud Images (https://cloud-images.ubuntu.com/).

Related branches

Akihiko Ota (sw37th) wrote :
Akihiko Ota (sw37th) wrote :
Akihiko Ota (sw37th) wrote :

And attached another patch which is support for Predictable Network Interface Names.
This patch fixes Bug #1716397 .

Akihiko Ota (sw37th) on 2017-10-15
summary: - DataSourceOpenNebula.py doesn't config network
+ DataSourceOpenNebula.py doesn't configure network
Scott Moser (smoser) on 2017-12-14
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
Chad Smith (chad.smith) on 2018-01-25
Changed in cloud-init:
status: Confirmed → Fix Committed
Chad Smith (chad.smith) wrote :

Hello Akihiko Ota, or anyone else affected,

As part of a stable release update, this changeset is committed and accepted cloud-init into artful-proposed and xenial-proposed as cloud-init version 17.2-35-gf576b2a2-0ubuntu1. The package is now available in the specific -proposed repository and can be installed and tested on artful and xenial instances with something like the following:

sed -i 's/ xenial / xenial-proposed /' /etc/apt/sources
sudo apt-get update
sudo apt-get install cloud-init;
sudo cloud-init clean --logs --reboot; # For a fresh install run

If there are concerns please comment on LP: #1747059.

Akihiko Ota (sw37th) wrote :

Hello Chad Smith,

I have updated cloud-init to 17.2-35-gf576b2a2-0ubuntu1 on xenial
and artful instances running in my OpenNebula environment. It's
working fine. Thank you!

This bug is believed to be fixed in cloud-init in 18.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments