fails to find bridge and storage pool when installing locally

[Brad Figg]

Fresh install of Bionic via MAAS with a zfsroot. I then installed conjure-up via "sudo snap install conjure-up --classic". I then run "sudo lxd init" and create a bridge and storage pool. Next, I run conjure-up and try to install "Canonical Distribution of Kubernetes". I choose the "Prometheus" and "Rancher" additional components. I then pick "localhost' as the target.

Conjure-up then fails with "Could not locate any network or storage devices to continue."

$ lxc network list
+--------+----------+---------+-------------+---------+
| NAME | TYPE | MANAGED | DESCRIPTION | USED BY |
+--------+----------+---------+-------------+---------+
| eno1 | physical | NO | | 0 |
+--------+----------+---------+-------------+---------+
| eno2 | physical | NO | | 0 |
+--------+----------+---------+-------------+---------+
| lxdbr0 | bridge | YES | | 0 |
+--------+----------+---------+-------------+---------+

$ lxc storage list
+---------+-------------+--------+--------------------------------+---------+
| NAME | DESCRIPTION | DRIVER | SOURCE | USED BY |
+---------+-------------+--------+--------------------------------+---------+
| default | | zfs | /var/lib/lxd/disks/default.img | 1 |
+---------+-------------+--------+--------------------------------+---------+

[Adam Stokes (adam-stokes)]

You wan to run `lxd.migrate` first, https://docs.conjure-up.io/devel/en/#users-of-lxd

[Brad Figg (brad-figg)]

This is a freshly installed system. What is there to "migrate"?

[Brad Figg (brad-figg)]

And, if this is a requirement why isn't conjure-up helping me with that? Why do I run conjure-up; fail due to known issue; quit conjure-up; fix issue; run conjure-up; run into next known issue; etc.?

[Cory Johns (johnsca)]

There was some confusion on Adam's part. The migrate step is only required if switching from the apt packaged lxd to the snap, which isn't required on bionic (but was on older releases).

From my own testing, the only way I could replicate this on a fresh bionic VM was to accept the default for IPv6 during the lxd init. It's mentioned in the error that IPv6 must be disabled, which comes from a limitation of Juju and is not the default during the lxd init process.

Brad, can you provide the output from the following:

  lxc network get lxdbr0 ipv6.address
  lxc network get lxdbr0 ipv6.nat

If those don't come back as "none" and "false", then you'll need to disable IPv6 with the command from the error:

  lxc network set lxdbr0 ipv6.address none ipv6.nat false

Adam: Instead of enabling the localhost cloud in the list only to fail once it's selected, maybe we can look at leaving it disabled if IPv6 is enabled and updating the message on highlight to indicate include the info about disabling IPv6?

[Cory Johns (johnsca)]

Oh, I forgot to mention that when Adam and I were discussing what was going on with this issue, he also pointed out that several people have had issues with CDK and ZFS recently (e.g., https://github.com/conjure-up/conjure-up/issues/1430) which are being still investigated, so even if you get past this bit, there's a fair chance it will fail during the deployment. If it does work, though, it would be great info for the k8s charm devs. We do know that dir storage works without issue.

[Brad Figg (brad-figg)]

@adam-stokes,

I reinstalled again. I purged the lxd deb packages and installed the lxd snap. I ran lxd.migrate which failed "unable to connect to socket". I ran lxd init setting up a bridge and storage pool. Then installed and ran conjure-up. Still hitting the exact same errors.

[Brad Figg (brad-figg)]

@johnsca,

That does appear to be the issue. Addressing ipv6 as you suggested got me past the error I was having. I'll continue on and see how things progress from here.

[Cory Johns (johnsca)]

For the record, I think the lxd.migrate requires that the deb packages still be installed (it's a transition step for the case where you were previously actively using the deb packaged lxd and want to move to the snap, so it has to be run after the snap install but prior to the deb removal). Hence the "unable to connect to socket" error.