We rely on backports in trusty for LXD 2.0.

On 3 June 2016 at 16:53, Blake Rouse <email address hidden> wrote:

> MAAS uses the cloud-image and we don't change the enabled repositories.
> That is something from the cloud images. Seems wierd that Juju is
> relying on backports anyway...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1568895
>
> Title:
>   Cannot add MAAS-based LXD containers in 2.0beta4 on trusty
>
> Status in cloud-images:
>   Confirmed
> Status in juju-core:
>   Invalid
> Status in MAAS:
>   Invalid
>
> Bug description:
>   Using:
>
>   $ juju version
>   2.0-beta4-xenial-amd64
>
>   built from commit dd9828ec7003d1a6ec1fc4dbcb7e6d17467a21f0
>
>   I am unable to add a LXD container using the following config:
>
>   bootstrap-timeout: 1800
>   enable-os-refresh-update: true
>   enable-os-upgrade: true
>   default-series: xenial
>   logging-config: <root>=DEBUG
>   lxc-clone: false
>   lxc-clone-aufs: false
>
>   Looking through machine-0.log I see the following repeated:
>
>   2016-04-11 14:48:02 INFO juju.utils.packaging.manager utils.go:98
> Retrying: &{/usr/bin/apt-get [apt-get
> --option=Dpkg::Options::=--force-confold
> --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install
> --target-release trusty-backports lxd] []  <nil> Reading package lists...
>   E: The value 'trusty-backports' is invalid for APT::Default-Release as
> such a release is not available in the sources
>   E: The value 'trusty-backports' is invalid for APT::Default-Release as
> such a release is not available in the sources
>
>   I tried adding lxd:0, lxc:0 and kvm:0 but only LXC was successful.
>
>   $ juju show-machines
>   model: admin
>   machines:
>     "0":
>       juju-status:
>         current: started
>         since: 11 Apr 2016 15:41:53+01:00
>         version: 2.0-beta4.1
>       dns-name: 10.17.20.201
>       instance-id:
> /MAAS/api/1.0/nodes/node-0d05c466-ffef-11e5-a124-52540098ca47/
>       machine-status:
>         current: running
>         message: Deployed
>         since: 11 Apr 2016 15:24:24+01:00
>       series: trusty
>       containers:
>         0/kvm/0:
>           juju-status:
>             current: pending
>             since: 11 Apr 2016 15:42:15+01:00
>           instance-id: pending
>           machine-status:
>             current: pending
>             since: 11 Apr 2016 15:42:15+01:00
>           series: trusty
>         0/lxc/0:
>           juju-status:
>             current: started
>             since: 11 Apr 2016 15:41:55+01:00
>             version: 2.0-beta4.1
>           dns-name: 10.17.20.202
>           instance-id: juju-machine-0-lxc-0
>           machine-status:
>             current: running
>             message: Container started
>             since: 11 Apr 2016 15:39:52+01:00
>           series: trusty
>           hardware: arch=amd64
>         0/lxd/0:
>           juju-status:
>             current: pending
>             since: 11 Apr 2016 15:32:05+01:00
>           instance-id: pending
>           machine-status:
>             current: pending
>             since: 11 Apr 2016 15:32:05+01:00
>           series: trusty
>       hardware: arch=amd64 cpu-cores=1 mem=1024M availability-zone=default
>       controller-member-status: has-vote
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-images/+bug/1568895/+subscriptions
>



-- 
Andrew McDermott <email address hidden>
Juju Core Sapphire team <http://juju.ubuntu.com>