Cloud-init incorrect openstack datasource on dpkg-reconfigure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Trusty |
Confirmed
|
Low
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned |
Bug Description
==== Begin SRU Template ====
[Impact]
When re-configuring cloud-init package by running dpkg-reconfigure, the OpenStack data source is incorrectly written to the configuration file /etc/cloud/
The result is that dpkg-reconfigure and selecting OpenStack results in non-functional openstack datasource.
[Test Case]
# launch a container
$ lxc launch ubuntu-daily:xenial x1
$ lxc exec x1 dpkg-reconfigure cloud-init
## Note that 'OpenStack' is not checked.
## Select OpenStack, hit enter
$ lxc exec x1 cat /etc/cloud/
# to update this file, run dpkg-reconfigure cloud-init
datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, MAAS, GCE, Openstack, CloudSigma, SmartOS, Ec2, CloudStack, None ]
Note, the reconfigured file was written, but contains 'Openstack' (lower case s), when OpenStack is what is needed.
When fixed, this will have 'OpenStack'.
[Regression Potential]
Regression potential would be limited to people running dpkg-reconfigure for cloud-init.
==== End SRU Template ====
On Ubuntu 14.04 LTS when re-configuring the cloud-init package by running dpkg-reconfigure, the OpenStack data source is incorrectly written to the configuration file /etc/cloud/
From a default install:
datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, MAAS, GCE, OpenStack, CloudSigma, Ec2, CloudStack, SmartOS, None ]
After running dpkg-reconfigure, selecting all options.
datasource_list: [ NoCloud, ConfigDrive, OpenNebula, Azure, AltCloud, OVF, MAAS, GCE, Openstack, CloudSigma, Ec2, CloudStack, SmartOS, None ]
Note that it reads "Openstack" instead of "OpenStack".
Related branches
no longer affects: | cloud-init |
Changed in cloud-init (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
Changed in cloud-init (Ubuntu Xenial): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Trusty): | |
status: | New → Confirmed |
importance: | Undecided → Low |
description: | updated |
This bug was fixed in the package cloud-init - 0.7.7~bzr1227- 0ubuntu1
--------------- bzr1227- 0ubuntu1) yakkety; urgency=medium
cloud-init (0.7.7~
* New upstream snapshot.
- fix one more unit test to run inside buildd.
-- Scott Moser <email address hidden> Sat, 04 Jun 2016 20:55:07 -0400