yahoo-eng-team team mailing list archive

[Simon Fels <1991051@xxxxxxxxxxxxxxxxxx>]

Turns out this a regression introduced of
https://bugs.launchpad.net/cloud-images/+bug/1988401

** Also affects: cloud-images
   Importance: Undecided
       Status: New

-- 
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/1991051

Title:
  Latest cloud-init release breaks Juju on LXD 4.0

Status in cloud-images:
  New
Status in cloud-init:
  Invalid
Status in lxd:
  New
Status in cloud-init package in Ubuntu:
  Triaged

Bug description:
  Ubuntu focal comes with LXD 4.0 installed by default. When using Juju
  to create containers on a local LXD with focal based instances, the
  deployment breaks due to and incorrect cloud-init configuration (see
  https://github.com/lxc/lxd/issues/10951, which existed since 2015!). A
  fix is not meant to arrive in LXD 4.0 till November (see
  https://github.com/lxc/lxd/issues/10951#issuecomment-1258691195).

  The new behavior in cloud-init has real implications as right now our
  commercial offering of the Anbox Cloud Appliance on the AWS
  marketplace (https://aws.amazon.com/marketplace/pp/prodview-
  aqmdt52vqs5qk) is broken when people buy it without a simple path to
  fix, other than forcing users to upgrade to LXD 5.0. We will hotfix
  this and ask people at installation time to upgrade to LXD 5.0.

  However, have we considered rolling back the cloud-init update as it's
  causing issues for a variety of people? I know about one other product
  which broke due to this (OSM).

  Also see https://bugs.launchpad.net/juju/+bug/1990594

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