mount-image-callback lxd: is broken with lxd 2.17

Bug #1715994 reported by Scott Moser on 2017-09-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-utils (Ubuntu)

Bug Description

mostly described at
lxd no longer has stopped containers mounted so this is broken.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cloud-image-utils 0.30-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 8 09:59:02 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (778 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
 PATH=(custom, no user)
SourcePackage: cloud-utils
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Scott Moser (smoser) wrote :
Changed in cloud-utils (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Scott Moser (smoser) wrote :

Marked as also affecting cloud-init as cloud-init's integration framework uses this functionality.
that framework is broken with newer versions of lxd.

Changed in cloud-utils:
status: New → Confirmed
importance: Undecided → Medium
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
Scott Moser (smoser) on 2017-10-25
no longer affects: cloud-init
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-utils - 0.30-0ubuntu3

cloud-utils (0.30-0ubuntu3) bionic; urgency=medium

  * sync to trunk at 322
    - mount-image-callback: run blockdev and udevadm settle on nbd devices.
      (LP: #1741096, #1741300)
    - mount-image-callback: Drop support for mounting lxd containers.
      (LP: #1715994)

 -- Scott Moser <email address hidden> Thu, 04 Jan 2018 14:17:26 -0500

Changed in cloud-utils (Ubuntu):
status: Confirmed → Fix Released
Scott Moser (smoser) on 2018-10-19
Changed in cloud-utils:
status: Confirmed → Fix Committed

This bug is believed to be fixed in cloud-utils in version 0.31. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-utils:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers