Exoscale datasource overwrites *all* cloud_config_modules

Bug #1841454 reported by Chris Glass on 2019-08-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Undecided
Unassigned

Bug Description

While testing the Exoscale datasource for its inclusion in a SRU, it was discovered that a cloud_config_module didn't work.

Passing user data such as: https://gist.github.com/chrisglass/fb0cf860be8cf01f456dfff8e162e004 results in the "runcmd" stanza not to be executed.

(feel free to get in touch should you like to play with an instance displaying the problem on Eoan)

Hypothesis:

The merge of the datasource's extra_config field (https://git.launchpad.net/cloud-init/tree/cloudinit/sources/DataSourceExoscale.py#n124) is erroneous: instead of *overwriting* the cloud_config_modules entry from the cloud.cfg file/user data, the cloud_config_modules should be *merged*.
An additional difficulty being that we insert a two-elements list (["set-passwords", "always"]) and it needs to be merge with a list containing just "set-passwords".

Related branches

This bug is fixed with commit d1b02221 to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=d1b02221

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

This bug is believed to be fixed in cloud-init in version 19.2-23. 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