Public bug reported: The new autopkgtests for the lxd provider are still not passing yet. The bridge setup looks like it works, but when juju comes to try and connect to lxd it is rejected on an http url.
<http://autopkgtest.ubuntu.com/packages/j/juju-core/> <https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/j/juju-core/20160415_081159@/log.gz> + juju bootstrap my-controller lxd --upload-tools --debug --config default-series=xenial 2016-04-15 07:59:35 INFO juju.cmd supercommand.go:60 running juju [2.0-beta4 gc go1.6.1] 2016-04-15 07:59:35 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a provider name 2016-04-15 07:59:35 INFO cmd cmd.go:141 no credentials found, checking environment 2016-04-15 07:59:35 DEBUG juju.cmd.juju.commands bootstrap.go:365 preparing controller with config: map[controller-uuid:644108a3-a3fc-4769-8e4f-c236232d4764 default-series:xenial type:lxd name:admin uuid:644108a3-a3fc-4769-8e4f-c236232d4764] 2016-04-15 07:59:39 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD remote "local": "" 2016-04-15 07:59:46 DEBUG juju.tools.lxdclient client.go:73 connecting to LXD remote "juju-remote": "10.0.8.1" 2016-04-15 07:59:47 ERROR cmd supercommand.go:448 Get https://10.0.8.1:8443/1.0/profiles: Forbidden adt-run [07:59:48]: test current-lxd-provider: -----------------------] adt-run [07:59:48]: test current-lxd-provider: - - - - - - - - - - results - - - - - - - - - - current-lxd-provider FAIL non-zero exit status 1 This is particularly confusing, as the exact same test passes if run on a canonistack machine using the ssh runner: <http://paste.ubuntu.com/15852422/> Test scripts are in the debian/tests directory of this packaging branch: <https://code.launchpad.net/~juju- qa/ubuntu/xenial/juju/xenial-2.0-beta4> >From discussion on irc earlier, the only way Tycho thought we could hit the >Forbidden here: [16:18] <tych0> mgz: so juju configures LXD to listen over HTTPS [16:18] <tych0> and if it accesses LXD via https, it needs to also configure LXD to recognize juju's cert [16:18] <tych0> it strikes me that that cert configuration has failed [16:19] <tych0> and that's why you get a 403 [16:19] <tych0> i'm not sure why you'd get it for any other reason ** Affects: juju-core Importance: Critical Status: Triaged ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: lxd-provider packaging ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Importance: Undecided => Critical ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Milestone: None => 2.0-rc1 ** Tags added: lxd-provider packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571082 Title: autopkgtest lxd provider tests fail for 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1571082/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
