Archlinux Bugs

Bug #1706593 reported by Rich Lees
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

This is a copy of an existing bug report, except the patch is created from the latest master and by myself who has signed the Canonical agreement.

Taken from:

I needed to patch a few places in distros/ to get cloud-init to work on Arch. This is with an OpenNebula-based cloud, but that shouldn't matter. In /etc/cloud/cloud.cfg I obviously used "arch" for system_info -> distro.

I checked against current trunk version of distros/ There's 3 issues in that this patch fixes (in order of appearance in the patch):

1. The loopback device is returned as an entry by net_util.translate_network(), leading to it gettingprocessed to configure settings like IP address, netmask, etc, but these aren't available and leads to an exception. I simply removed the "lo" entry from the dictionary.

2. The netctl command expects its profile files to be named /etc/netctl/<iface>. The code in leaves out the last separator, leading to files like /etc/netctleth0, which doesn't work

3. The function convert_resolv_conf() can't possibly work, as it tries to iterate over the "list" type instead of the "settings" list.

Related branches

Revision history for this message
Rich Lees (rlees85) wrote :
Revision history for this message
Scott Moser (smoser) wrote :

I'd put a bit of work into the arch code (discussion that lead to it at [1]).
See my branch [2] which I'm pretty sure fixes '2' and '3' above, and adds some unit tests that can be extended to fix and validate '1'.

I can add the change for '1' , and submit a merge proposal if you (Rich) will review and validate.


Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Rich Lees (rlees85) wrote :

Hi Scott,

Thanks for the reply.

I agree that:

Solves issue 2 (and probably loads of other things that are not listed here).

Issue 3 is already solved on Master and I can't see how the changes you make affect that.

I would be more than happy to review/validate/test locally if you were to extend the existing/create a new merge to fix issue 1.

Revision history for this message
Scott Moser (smoser) wrote :

The fix for 1 (loopback device) and 2 (path for netctl config) are in

You're right about 3. I'm not sure when that got fixed, looking at logs I dont see it quickly. But I dont think it is a problem now, and the test I've added verifies a simple nameserver field gets populated.

Please go ahead and comment in the merge proposal and I can pull that.

Scott Moser (smoser)
Changed in cloud-init:
status: Confirmed → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Cloud-init 17.1

This bug is believed to be fixed in cloud-init in 17.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
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.