Can not clone lxc container with lvm backingstore after ubuntu update

[questioner]

lxc-clone -s -K -M -H -o debian7 -n debian7-bak

lxc_container: bdev.c: mount_unknown_fs: 209 failed to determine fs type for '/dev/vg/debian7'
lxc_container: bdev.c: detect_fs: 320 failed mounting /dev/vg/debian7 onto /container/debian7/debian7 to detect fstype
lxc_container: bdev.c: detect_fs: 298 child exited early - fstype not found
lxc_container: bdev.c: bdev_copy: 3090 failed getting pathnames for cloned storage: /dev/vg/debian7
lxc_container: lxccontainer.c: copy_storage: 2489 Error copying storage clone failed

Aptitude LOG

[AKTUALISIERUNG] landscape-common:amd64 14.01-0ubuntu3 -> 14.12-0ubuntu0.14.04
[AKTUALISIERUNG] libelf1:amd64 0.158-0ubuntu5.1 -> 0.158-0ubuntu5.2
[AKTUALISIERUNG] libevent-2.0-5:amd64 2.0.21-stable-1ubuntu1 -> 2.0.21-stable-1ubuntu1.14.04.1
[AKTUALISIERUNG] liblxc1:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1
[AKTUALISIERUNG] libmysqlclient18:amd64 5.5.40-0ubuntu0.14.04.1 -> 5.5.41-0ubuntu0.14.04.1
[AKTUALISIERUNG] lxc:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1
[AKTUALISIERUNG] lxc-templates:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1
[AKTUALISIERUNG] mysql-common:amd64 5.5.40-0ubuntu0.14.04.1 -> 5.5.41-0ubuntu0.14.04.1
[AKTUALISIERUNG] python-apt:amd64 0.9.3.5 -> 0.9.3.5ubuntu1
[AKTUALISIERUNG] python-apt-common:amd64 0.9.3.5 -> 0.9.3.5ubuntu1
[AKTUALISIERUNG] python3-apt:amd64 0.9.3.5 -> 0.9.3.5ubuntu1
[AKTUALISIERUNG] python3-lxc:amd64 1.0.6-0ubuntu0.1 -> 1.0.7-0ubuntu0.1

Trusty update 3.13.0-44-generic #73-Ubuntu SMP

[Stéphane Graber (stgraber)]

May be related to https://github.com/lxc/lxc/issues/406

[questioner (stacker)]

May be related to the apparmor "profile_replace"?

Same update:
kernel: [819239.355418] type=1400 audit(1422103541.577:177): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default" pid=5095 comm="apparmor_parser"
kernel: [819239.355530] type=1400 audit(1422103541.577:178): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-with-mounting" pid=5095 comm="apparmor_parser"
kernel: [819239.355641] type=1400 audit(1422103541.577:179): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="lxc-container-default-with-nesting" pid=5095 comm="apparmor_parser"
kernel: [819239.375656] type=1400 audit(1422103541.597:180): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/bin/lxc-start" pid=5097 comm="apparmor_parser"

[Serge Hallyn (serge-hallyn)]

Probably not related to issue 406, as this is a debian container.

[Serge Hallyn (serge-hallyn)]

Patch to fix this has been posted to the mailing list.

[questioner (stacker)]

Can't find it on the mailing list.
The container is NOT an unprivileged container.
There is no "lxc.id_map" in the configuration.
It is a "dowloaded" debian 7 container, all standard.

[Serge Hallyn (serge-hallyn)]

The patch is here:

https://lists.linuxcontainers.org/pipermail/lxc-devel/2015-January/011289.html

You should be able to work around it by doing

sudo mkdir /var/lib/lxc/debian7/debian7

 status: fixcommitted

[questioner (stacker)]

Workaround doing fine. I'll test the fix with the next release.