[SRU] xenial cloud-init update
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Xenial |
Fix Released
|
High
|
Scott Moser | ||
| Yakkety |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
---- Begin SRU Template ----
[Impact]
Please see individual bugs listed for impact. Some significant fixes added here are:
- user_data: fix error when user-data is not utf-8 decodable (LP: #1532072)
- support networking information being read from dreamcompute and older
versions of openstack.
- support reading and applying networking information on SmartOS virtual
machine guests.
- fix reading networking from openstack network_data.json
- support for renaming devices in a container (LP: #1579130).
- remove blocking of udev rules (LP: #1577844, LP: #1571761)
- Apt sources configuration improvements (LP: #1574113)
- cloud-config specified on kernel command line will now override
system settings (LP: #1582323).
- Paths: fix instance path if datasource's id has a '/'. (LP: #1575938)
- Config Drive: fix check_instance_id signature. (LP: #1575055)
[Test Case]
Most of the changes here are related to data provided by the cloud and properly configuring an instance in response to that data.
Platforms:
Azure
NoCloud with network_config
NoCloud without network_config
Google GCE
Openstack Config Drive
Openstack Metadata Service
LXD
Joyent
Dreamcompute
MAAS (ephemeral env and installed environment)
For each of these platforms, the following should be done once with user-data provided and once without.
- Boot the latest available xenial instance (1 with user-data, 1 without)
- Enable proposed and upgrade
- save original /var/log/
- reboot, check /var/log/
this checks that the upgrade from a previous version did not recognize any
failures.
- clean the instance to make it seem as much as possible like a first boot.
( cd /var/lib/cloud && for d in *; do [ "$d" = "seed" ] || rm -Rf "$d"; done )
- reboot, check /var/log/
this mimics first boot in as close to a real scenario as possible without generating new images with the patched cloud-init.
- reboot again, check /var/log/
this time check for second-boot issues.
[Regression Potential]
The changes here that are most likely to cause regression are those related to network configuration. cloud-init is now doing a better job of configuring the sytem as the datasource indicated it should be configured. That could, however, have fallout network would be configured differently than before.
[Other Info]
This does represent significant changes. Cloud-init is stabalizing toward a 0.7.8 release, and it is important to get these changes out. They are present in yakkety, and available in a daily ppa at https:/
---- End SRU Template ----
There are several fixes in the current yaketty version of cloud-init that need to make it back to 16.04. These are both bug fixes and more general improvements in code.
This bug is a 'SRU metabug' to cover that SRU. Below is a changelog format with individual bugs listed. The uploaded version will have the bug references removed, but I will mark bugs individually as fix-released and reference this bug.
* debian/
passed in as an argument.
* New upstream snapshot.
- user_data: fix error when user-data is not utf-8 decodable (LP: #1532072)
- write_files: if no permissions are provided, use the default without
logging a warning.
- do not write /etc/systemd/
(LP: #1594546)
- fix several potential errors identified by pylint.
- move 'main' into cloudinit/cmd/ for easier testing
- Remove trailing dot from GCE metadata URL (LP: #1581200) [Phil Roche]
- Refactor cloudinit networking module to improve testing
- Change missing Cheetah log warning to debug [Andrew Jorgensen]
- network configuration improvements
- centrally handle 'dsmode' (DataSource mode) to be 'local' or 'net.
- support networking information being read on dreamcompute
- support reading and applying networking information on SmartOS
- improve reading networking from openstack network_data.json
- support for renaming devices in a container (LP: #1579130).
- remove blocking of udev rules (LP: #1577844, LP: #1571761)
- Apt sources configuration improvements (LP: #1574113)
- cloud-config specified on kernel command line will now override
system settings (LP: #1582323).
- fix timestamp in reporting events.
- Paths: fix instance path if datasource's id has a '/'. (LP: #1575938)
- Config Drive: fix check_instance_id signature. (LP: #1575055)
- cloudstack: Only use DHCPv4 lease files as a datasource (LP: #1576273)
Related branches
| Changed in cloud-init: | |
| status: | New → Fix Released |
| importance: | Undecided → High |
| no longer affects: | cloud-init |
| Changed in cloud-init (Ubuntu Yakkety): | |
| status: | New → Fix Released |
| importance: | Undecided → Medium |
| Changed in cloud-init (Ubuntu Xenial): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| summary: |
- xenial cloud-init update + [SRU] xenial cloud-init update |
| description: | updated |
| Changed in cloud-init (Ubuntu Xenial): | |
| assignee: | nobody → Scott Moser (smoser) |
| Chris J Arges (arges) wrote Please test proposed package | #1 |
| Changed in cloud-init (Ubuntu Xenial): | |
| status: | In Progress → Fix Committed |
| tags: | added: verification-needed |
| Chris J Arges (arges) wrote | #2 |
| Scott Moser (smoser) wrote | #3 |
| Patricia Gaughen (gaughen) wrote | #4 |
| Scott Moser (smoser) wrote | #5 |
| Scott Moser (smoser) wrote | #6 |
| tags: |
added: verification-done removed: verification-needed |
| Juan J. Martínez (jjmartinez) wrote | #7 |
| Launchpad Janitor (janitor) wrote | #9 |
| Changed in cloud-init (Ubuntu Xenial): | |
| status: | Fix Committed → Fix Released |
| Chris J Arges (arges) wrote Update Released | #10 |
Hello Scott, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-
Further information regarding the verification process can be found at https:/