conjure-up openstack always fails when lxd uses btrfs

[aijanai]

Report

Thank you for trying conjure-up! Before reporting a bug please make sure you've gone through this checklist:

• [no] Is this problem already documented at https://docs.ubuntu.com/conjure-up/en/troubleshoot#common-spell-problems
• [yes] Is conjure-up running inside a virtual machine?
• [yes] Is this problem reproducible with sudo snap refresh conjure-up --edge?

Please provide the output of the following commands

which juju
/snap/bin/juju

juju version
2.3.3-xenial-amd64

which conjure-up
/snap/bin/conjure-up

conjure-up --version
conjure-up 2.5.5

which lxc
/snap/bin/lxc

/snap/bin/lxc config show
config:
  core.https_address: '[::]'

/snap/bin/lxc version
2.21

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

conjure-up.tar.gz

Sosreport

Please attach a sosreport:

sosreport (version 3.5)

no valid plugins were enabled

What Spell was Selected?

Openstack

What provider (aws, maas, localhost, etc)?

localhost (AWS EC2 c5.4xlarge, 16CPU, 32GB RAM, 200GB SSD)

Commands ran

the history from the EC2 machine inception

    1  sudo apt update
    2  sudo apt remove --purge lxd lxd-client
    3  sudo apt upgrade
    4  which lxd
    5  sudo snap install lxd
    6  sudo snap install conjure-up --classic

then comes the refresh to latest conjure up version and lxd initialization

ubuntu@ip-172-31-45-90:~$ sudo snap refresh conjure-up --edge
conjure-up (edge) 2.5.5-20180302.1803 from 'canonical' refreshed
ubuntu@ip-172-31-45-90:~$ lxd init
Do you want to configure a new storage pool (yes/no) [default=yes]?
Name of the new storage pool [default=default]:
Name of the storage backend to use (dir, btrfs, ceph, lvm) [default=btrfs]:
Create a new BTRFS pool (yes/no) [default=yes]?
Would you like to use an existing block device (yes/no) [default=no]?
Size in GB of the new loop device (1GB minimum) [default=38GB]:
Would you like LXD to be available over the network (yes/no) [default=no]?
Would you like stale cached images to be updated automatically (yes/no) [default=yes]?
Would you like to create a new network bridge (yes/no) [default=yes]?
What should the new bridge be called [default=lxdbr0]?
What IPv4 address should be used (CIDR subnet notation, “auto” or “none”) [default=auto]?
What IPv6 address should be used (CIDR subnet notation, “auto” or “none”) [default=auto]? none
LXD has been successfully configured.

Additional Information

This never happens when LXD uses dir or zfs drivers for the storage pool. It consistently happens when using btrfs.
On a side note, when LXD uses lvm, conjure-up hangs on lvcreate, which stays stuck in D state on ps output.

Being this the scope of a test of Openstack deployment, I'd rather put diras default LXD driver, not btrfs.

[aijanai]

bump

[ToniIltanen]

I can verify this, installation fails for me on deployment to juju service giving an error status. with zfs everything goes like it should.

[adam-stokes]

Can you juju ssh <unit>/0; and sudo pastebinit /var/log/unit*.log - being the name of the application in the error state