cloud-init 24.3
Milestone information
- Project:
- cloud-init
- Series:
- trunk
- Version:
- 24.3
- Released:
- Registrant:
- Chad Smith
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
Cloud-init release 24.3 is now available
The 24.3 release:
* spanned about 8 weeks
* had 18 contributors
* fixed 21 github issues
Highlights:
- Add AOSC linux distribution support (#5310)
- Add OpenEuler support for cc_spacewalk module (#5530)
- Add network-config seed support for nocloud datasource (#5566)
- Support remote URI sources write_files module (#5505)
- Bootspeed improvement: support for socket-based shared python process
across cloud-init boot stages (#5595)
- Add trace-level logger (#5414)
- Yum support for setting mirrorlist or baseurl (#5522))
- Azure preliminary support of optional AzureProxyAgent (#5601)
- WSL support multi-part MIME config parts as well as landscape tags for
provisioning (#5460, #5538)
- avoid snap refresh on package_upgrade: true when snap refresh is held
- optimization: eliminate redundant config reads across boot stages (#5536)
- provide option to set empty passwords and fix password unlock when
lock_passwd: False on Alpine/
Bug fixes:
- NetworkManager network v1 rendering of config ensure bond- prefix
- collect-logs avoid inclusion of sensitive data updated apport intregration
Breaking Changes:
- Warning issued for systemd environments if cloud-init boot stages are
called by PIDs other than the root process. It is expected that boot
stages are only called by systemd units and not post-production scripts
or tools.
Changelog
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.