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.
Report
Thank you for trying conjure-up! Before reporting a bug please make sure you've gone through this checklist:
sudo snap refresh conjure-up --edge
?Please provide the output of the following commands
conjure-up.tar.gz
Sosreport
Please attach a sosreport:
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
then comes the refresh to latest conjure up version and lxd initialization
Additional Information
This never happens when LXD uses
dir
orzfs
drivers for the storage pool. It consistently happens when usingbtrfs
. On a side note, when LXD useslvm
, conjure-up hangs onlvcreate
, which stays stuck inD
state onps
output.Being this the scope of a test of Openstack deployment, I'd rather put
dir
as default LXD driver, notbtrfs
.