Public bug reported:

by default lxc containers do not allow mounting ext4 filesystems.
during 'maas-import-ephemerals', maas uses mount to mount an ext4 
filesystem-in-a-file to convert the ephemeral image that it downloads from 
http://maas.ubuntu.com/images into a -root.tar.gz file that curtin will use for 
installation.

In the end, try to do this, and you'll see something like:

Tue, 03 Dec 2013 17:17:57 +0000: converting 
/var/lib/maas/ephemeral/precise/ephemeral/amd64/20131010/disk.img to 
/var/lib/maas/ephemeral/precise/ephemeral/amd64/20131010/dist-root.tar.gz
mount: Could not find any loop device. Maybe this kernel does not know
       about the loop device? (If so, recompile or `modprobe loop'.)
Tue, 03 Dec 2013 17:17:57 +0000: failed to mount 
/var/lib/maas/ephemeral/precise/ephemeral/amd64/20131010/disk.img


http://askubuntu.com/questions/376345/allow-loop-mounting-files-inside-lxc-containers
describes how to modify a container to allow mount.

It is possible that lxc could allow mount of ext4 filesytems inside a
container by default.  I will open a task for lxc for that.  However,
even if it did, the user-namespace'd lxc container that we should have
in 14.04 will not work with that.

Attached is instructions on how to recreate this on 12.04 (using cloud-
archive).  The same should basically work on trusty (using trusty).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas-cluster-controller 1.4+bzr1693+dfsg-0ubuntu2
ProcVersionSignature: Ubuntu 3.12.0-4.12-generic 3.12.1
Uname: Linux 3.12.0-4-generic x86_64
ApportVersion: 2.12.7-0ubuntu1
Architecture: amd64
Date: Tue Dec  3 17:34:18 2013
Ec2AMI: ami-00000611
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.tiny
Ec2Kernel: aki-00000548
Ec2Ramdisk: ari-00000548
PackageArchitecture: all
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.maas.maas.local.celeryconfig.cluster.py:
 # UUID identifying the running cluster controller.
 CLUSTER_UUID = '5ccc848a-7a39-4dd5-af61-ad1fa19d183b'
mtime.conffile..etc.maas.maas.cluster.conf: 2013-12-03T17:22:55.003463
mtime.conffile..etc.maas.maas.local.celeryconfig.cluster.py: 
2013-12-03T17:22:55.003463
upstart.isc-dhcp-server.override: manual

** Affects: maas
     Importance: Undecided
         Status: Confirmed

** Affects: lxc (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Affects: maas (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: amd64 apport-bug ec2-images trusty

** Attachment added: "instructions for recreating failure"
   
https://bugs.launchpad.net/bugs/1257389/+attachment/3922253/+files/maas-lxc-bug.txt

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1257389

Title:
  cannot run maas-import-ephemerals inside lxc container

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1257389/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to