root-disk too small when using LXC as hypervisor

[Andreas Hasenack]

Inside the newly launched instance (a container):
root@juju-fakestack-machine-0:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/nbd2 1.4G 911M 358M 72% /
tmpfs 64K 0 64K 0% /sys/fs/cgroup
devfs 64K 4.0K 60K 7% /dev
none 1.6G 100K 1.6G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 7.9G 0 7.9G 0% /run/shm
none 100M 0 100M 0% /run/user

The "disk" file on the outside that qemu-nbd is pointing at:
10550 ? Ssl 0:05 /usr/bin/qemu-nbd -c /dev/nbd2 /var/lib/nova/instances/fb809be7-5b42-4ac2-a164-59dc17078ae5/disk

root@flexible:/var/lib/nova/instances/fb809be7-5b42-4ac2-a164-59dc17078ae5# du -hs *
0 console.log
250M disk
4.0K disk.info
4.0K libvirt.xml
4.0K rootfs
root@flexible:/var/lib/nova/instances/fb809be7-5b42-4ac2-a164-59dc17078ae5# qemu-img info disk
image: disk
file format: qcow2
virtual size: 20G (21474836480 bytes)
disk size: 258M
cluster_size: 65536
backing file: /var/lib/nova/instances/_base/b5a426bcf77b13a86933a29e420e7a89e00da589
Format specific information:
    compat: 1.1
    lazy refcounts: false
root@flexible:/var/lib/nova/instances/fb809be7-5b42-4ac2-a164-59dc17078ae5#

The image this container was launched with came from this tarball:
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64.tar.gz

The image, when uploaded to glance, had a rootfs size constraint of 10G applied, so juju picked the right image.

I'm guessing a partition/fs resize that happens normally with kvm images doesn't work when using lxc, or is not applied.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.