cloud-init:ubuntu/kinetic

Last commit made on 2023-01-10
Get this branch:
git clone -b ubuntu/kinetic https://git.launchpad.net/cloud-init
Members of cloud-init Commiters can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:
ubuntu/kinetic
Repository:
lp:cloud-init

Recent commits

e8a1f2c... by Chad Smith

update changelog

4d0fb3b... by Chad Smith

Add patch retain-netplan-world-readable.patch

Keep /etc/netplan/50-cloud-init.yaml as world-readable.
Backport of 9e6f7ed6e.

5213618... by James Falcon

releasing cloud-init version 22.4-0ubuntu0~22.10.1

197b7fd... by Chad Smith

changelogs: sync released hotfix d/changelog entries and Changelog

d3a523e... by James Falcon

update changelog

0db934e... by James Falcon

Merge main at '22.4' into ubuntu/kinetic

85e86e5... by James Falcon

Release 22.4 (#1832)

Bump the version in cloudinit/version.py to 22.4 and
update ChangeLog.

fe115f9... by Alberto Contreras

test: fix pro integration test

Ensure Pro instances are detached before the test run and
that the test only runs on LTS releases.

As ua.UserFacingError is not properly converted to str,
manually pick its msg to provide the user a more informative
logging msg.

7b04985... by Dermot Bradley

cc_disk_setup: pass options in correct order to utils (#1829)

When testing cc_disk_setup it failed with the following error:

  Unexpected error while running command.
  Command: ['/sbin/mkfs.ext4', '/dev/sdc1', '-L', 'disk3-fs2']
  Exit code: 1
  Reason: -
  Stdout:
  Stderr: mke2fs 1.46.5 (30-Dec-2021)
          mkfs.ext4: invalid blocks '-L' on device '/dev/sdc1'

The manpages for mkfs.ext4, mkfs.xfs, and mkswap all indicate that
options should be passed *before* the device name but cc_disk_setup
passed them after the device name - in the case of mkfx.ext4 a
"fs-size" can be passed after the device and that is what the
"-L disk3-fs2" option is being misintepreted as.

This PR ensures that the device name is passed last. The underlying
issue appears to be due to a different in behaviour between glibc and
musl where glibc "helps" applications by re-ordered command-line
parameters by musl does not[1] as it sticks to POSIX spec.

This PR also modifies 2 testcases to cater for this change in the code,
adds a note to disk_setup to clarify that when creating a swap partition
a fs_entry also needs to be specified so that mkswap is run, adds to the
examples how to specify a non-default partition type (i.e. for swap),
and modifies the description for disk_setup to clarify this.

[1] https://wiki.musl-libc.org/functional-differences-from-glibc.html#Miscellaneous_functions_with_GNU_quirks

fe3dbc2... by Chad Smith

tests: text_lxd basic_preseed verify_clean_log (#1826)