[10:48] <Fallenour> Im having issues getting lxd containers to install in my juju instances. I see this has been a bug in the past from 2017, and appears to still be a problem. Can anyone make any recommendations?
[21:39] <Fallenour> is anyone on
[21:39] <Fallenour> Ive run into a pretty serious issue with juju, and I could really use some help. Its completely blocking me from being able to build or deploy anything.
[22:02] <pmatulis> Fallenour, check logs, look for errors
[22:02] <Fallenour> there arent any
[22:02] <Fallenour> Thats the weirdest part. All it says is the same error over and over again, Image cant be found
[22:03] <pmatulis> using MAAS as the backing cloud?
[22:03] <Fallenour> I tried Juju, I tried conjure up, I even tried just deploying a basic lxd container. All failed, All same issue.
[22:03] <Fallenour> yea, howd you know?
[22:03] <Fallenour> I saw several tickets outstanding for the issue, but no solution
[22:03] <pmatulis> go to MAAS and try to Deploy on a node. so no Juju, just MAAS
[22:04] <Fallenour> I swear by the old gods and the new, I will get this working, and i will deploy it as part of my hybrid cloud solution I made, even if I have to fly to canonicals doorstep and kick it in, drag out the engineers, and build it in the parking lot.
[22:04] <Fallenour> It deploys nodes just fine
[22:04] <Fallenour> its only the containers
[22:04] <Fallenour> juju is magic, I just want it to work :(
[22:05] <Fallenour> they all fail when deploying containers
[22:05] <pmatulis> enter the deployed MAAS node and try to use LXD manually
[22:05] <Fallenour> bare metal, and 18.04LTS and 16.04LTS deployments of the base OS works fine.
[22:05] <Fallenour> I tried that. It failed.
[22:05] <Fallenour> same error when I use juju
[22:05] <pmatulis> so it's not a Juju problem then
[22:06] <Fallenour> its gotta be a juju issue
[22:06] <Fallenour> when I ssh into the box, and use LXD locally, it works
[22:06] <pmatulis> well that's what i asked you to do. you said it didn't work
[22:06] <Fallenour> And all my systems deployed by maas outside of juju deploy LXD containers just fine
[22:06] <Fallenour> oooo
[22:06] <Fallenour> sorry
[22:06] <Fallenour> yea, maas let me build them just fine
[22:07] <Fallenour> its actualyl why I migrated the existing lxd systems into juju, because they worked.
[22:07] <Fallenour> wonky with ceph, and wont work in clustered modes with ceph directly, but they do work, so I figured Id figure that issue out later.
[22:07] <pmatulis> pastebin exactly what you're trying with Juju. exact commands and output. starting from the bootstrap command
[22:08] <Fallenour> maas and juju clouds are already built, and work fine
[22:08] <Fallenour> ill start with the add-model
[22:08] <Fallenour> juju add-model cloud-000-000001
[22:08] <Fallenour> then I do
[22:08] <Fallenour> juju deploy cs:bundle/openstack-base-61
[22:09] <Fallenour> it begins by deploying the 4 maas servers, installing ubuntu 18.04LTS, which succeeds, which juju shows as deployed. Then it begins by deploying services
[22:09] <Fallenour> everyting outside of containers deploys successfully, but anythingg in the containers, or the containers themselves, all fail
[22:10] <Fallenour> Ive got this error: WARNING juju.provisioner incomplete DNS config found, discovering host's DNS config
[22:10] <Fallenour> but when I check maas, its got several DNS servers set
[22:11] <Fallenour> and I can ping google, both from the device deploying to juju, and from the machine itself
[22:11] <Fallenour> I tested that by doing: juju ssh 0
[22:11] <Fallenour> and then pinging google.