[Bug 2049860] Re: cloud-init cloud-config for ssh broken in jammy
Launchpad Bug Tracker
2049860 at bugs.launchpad.net
Mon Feb 5 05:26:56 UTC 2024
This bug was fixed in the package livecd-rootfs - 2.765.38
---------------
livecd-rootfs (2.765.38) jammy; urgency=medium
* Add a largemem subarch for ubuntu-server that ships a 64k kernel variant
by default (LP: #2050209)
livecd-rootfs (2.765.37) jammy; urgency=medium
* fix: Fix for calling unminimize if lxd-installer package
not installed. (LP: #2049723)
livecd-rootfs (2.765.36) jammy; urgency=medium
* Use correct /etc/ssh/sshd_config.d/ filename so cloud-init overrides
via cloud-config works. (LP: #2049860)
-- Ćukasz 'sil2100' Zemczak <lukasz.zemczak at ubuntu.com> Thu, 25 Jan
2024 11:46:49 +0100
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2049860
Title:
cloud-init cloud-config for ssh broken in jammy
Status in cloud-images:
Fix Committed
Status in cloud-images focal series:
New
Status in livecd-rootfs package in Ubuntu:
New
Status in livecd-rootfs source package in Focal:
Fix Committed
Status in livecd-rootfs source package in Jammy:
Fix Released
Bug description:
[impact]
cloud-config overrides via cloud-init for ssh do no longer work. Eg.
#cloud-config
ssh_pwauth: True
doesn't enable password authentication anymore.
The reason is that https://git.launchpad.net/livecd-
rootfs/commit/live-build/ubuntu-
cpc/hooks.d/chroot/052-ssh_authentication.chroot?h=ubuntu/jammy&id=3b2eeb017153cbbfc8935f9447e00d196e34d983
is a wrong backport using the wrong filename
/etc/ssh/sshd_config.d/10-cloudimg-settings.conf . it needs to be
/etc/ssh/sshd_config.d/60-cloudimg-settings.conf . See
https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
cpc/hooks.d/chroot/052-ssh_authentication.chroot?h=ubuntu/master which
is the correct change in the ubuntu/master branch.
This bug needs only fixing in Jammy and Focal because the fix is
correct in > Jammy. Jammy has this bug already in the -updates pocket
but Focal only has the wrong fix in its git branch.
[test plan]
* build an image with the proposed fix
* use a cloud-init cloud-config data to enable ssh password auth (which is disabled by default)
* check after image boot with "sshd -T" if password authentication is enabled
* make sure that the file written by cloud-init in /etc/ssh/sshd_config.d/ has a lower number than the file from the image (cloudimg-settings.conf)
[ Where problems could occur ]
The change does rename a single file to have correct ordering between the prebuilt cloud images and cloud-init. There are edge-cases where this could create problems but those are acceptable:
- rebuilt images based on the Ubuntu image which try to delete
10-cloudimg-settings.conf would no longer work
But in general this is a bug fix for the changes introduced in
LP:#1968873
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2049860/+subscriptions
More information about the foundations-bugs
mailing list