cloud-init

OpenNebula network configuration is ignored for distros with predictable interface names.

Bug #1716397 reported by Enol Fernández on 2017-09-11

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cloud-init	Fix Released	Medium	Enol Fernández

Bug Description

OpenNebula network configuration is provided in context with device identifiers in the form ETH[0-9] but with newer distros using predictable interface names this configuration is no longer applied and device MAC should be checked instead of the identifier.

Even when providing matching device name, this information is not being correctly propagated by the OpenNebula data source to the other cloud-init modules

Related branches

~chad.smith/cloud-init:ubuntu/devel

Merged into cloud-init:ubuntu/devel at revision 8459712e8d3b37d4efb5b89aab71f35e000daf6f

Server Team CI bot: Approve (continuous-integration) on 2018-01-25

Scott Moser: Pending requested 2018-01-25

~sw37th/cloud-init:fix_for_opennebula

Merged into cloud-init:master at revision 8a9421421497b3e7c05589c62389745d565c6633

Scott Moser: Approve on 2018-01-24

Server Team CI bot: Needs Fixing (continuous-integration) on 2017-12-21

Scott Moser (smoser) on 2017-09-11

Changed in cloud-init:
status:	New → Confirmed
importance:	Undecided → Medium
assignee:	nobody → Enol Fernández (enolfc)

Revision history for this message

Akihiko Ota (sw37th) wrote on 2017-12-02:

https://bugs.launchpad.net/cloud-init/+bug/1719157/comments/3

I wrote a patch which supports Predictable Network Interface Names for DataSourceOpenNebula.py.
Please try it.

Chad Smith (chad.smith) on 2018-01-25

Changed in cloud-init:
status:	Confirmed → Fix Committed

Revision history for this message

Chad Smith (chad.smith) wrote on 2018-02-14:

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.

Revision history for this message

Scott Moser (smoser) wrote on 2018-02-22: Fixed in Cloud-init 18.1

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.