yahoo-eng-team team mailing list archive

[Chad Smith <2001737@xxxxxxxxxxxxxxxxxx>]

work in progress pull request which will resolve this problem. Needs unit tests and then cloud-init can support jammy launches from LXD 4.0 hosts.
https://github.com/canonical/cloud-init/pull/1948

** Changed in: cloud-init
       Status: Triaged => Won't Fix

** Changed in: cloud-init
       Status: Won't Fix => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2001737

Title:
  Jammy's cloud-init doesn't work on lxd 4.0

Status in cloud-init:
  In Progress

Bug description:
  When trying to boot a Jammy container on a host that uses lxd/4.0 the
  cloud-init there fails to work properly.

  The result is, that a ssh key for authentication isn't inserted in the
  host, denying ssh access.

  Upgrading to lxd/5.0 does works around this issue, which provides a
  newer interface, but isn't a solution as lxd/4.0 is an LTS of only a
  few years old.

  For a complete log see: https://pastebin.canonical.com/p/X9GN5GH8wv/

  To reproduce, install the lxd 4.0/stable snap on a machine, configure
  it to inject a ssh key, and try to launch an jammy container there.
  One won't be able to ssh into the container.

  An extensive thread about this can be found at:
  https://chat.canonical.com/canonical/pl/c1erobjybt8jzbgxguowxrddrc

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2001737/+subscriptions