yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1894887@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

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

Title:
  cloud-init's cc_lxd module fails to create a lxd bridge when running
  against lxd 4.0.3

Status in cloud-init:
  Expired

Bug description:
  Between 3.0.3 (the lxd version in bionic) and 4.0.3 (the lxd version
  in focal), lxd has addressed an internal accounting bug regarding
  network interfaces and profiles.

  Specifically, this means that after `lxd init --auto --storage-backend
  dir` on each system, we see different output for `lxc network show
  lxdbr0`.  On 3.0.3, it includes this line:

    used_by: []

  whereas on 4.0.3, it includes:

    used_by:
    - /1.0/profiles/default

  It's important to note that on _both_ versions, `lxc profile show
  default` indicates that `lxdbr0` is used by the default profile; the
  change is that lxd now accurately tracks this fact when examining
  `lxdbr0`.

  This change also means that `lxdbr0` cannot be removed immediately:
  you first have to remove it from the default profile.  Currently,
  cloud-init removes it without attempting to remove it from the default
  profile first.  Removal fails (and is ignored, which may be a separate
  bug), so when we go to create the network, lxd gives us: "Error: The
  network already exists"

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