Cannot add MAAS-based LXD containers in 2.0 on trusty

[Andrew McDermott]

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

[Andrew McDermott (frobware)]

Correction, KVM containers are fine too.

$ 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: started
          since: 11 Apr 2016 15:50:25+01:00
          version: 2.0-beta4.1
        dns-name: 10.17.20.203
        instance-id: juju-machine-0-kvm-0
        machine-status:
          current: allocating
          message: Creating container; it might take some time
          since: 11 Apr 2016 15:48:04+01:00
        series: trusty
        hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
      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

[Andrew McDermott (frobware)]

My MAAS setup is using:

 http://maas.ubuntu.com/images/ephemeral-v2/releases/

for images, and were synced today:

14.04 LTS amd64 558.7 MB 4 Mon, 11 Apr. 2016 15:17:26

[Andrew McDermott (frobware)]

I bootstrapped, then added a container (juju add-machine lxd:0)

This was failing as before. I manually added:

 deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse

to /etc/apt/sources.list as Juju and everything kicked into life:

$ juju show-machines
model: admin
machines:
  "0":
    juju-status:
      current: started
      since: 11 Apr 2016 20:16:10+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 20:16:09+01:00
    series: trusty
    containers:
      0/lxd/0:
        juju-status:
          current: started
          since: 11 Apr 2016 20:26:30+01:00
          version: 2.0-beta4.1
        dns-name: 10.17.20.202
        instance-id: juju-machine-0-lxd-0
        machine-status:
          current: running
          message: Container started
          since: 11 Apr 2016 20:26:01+01:00
        series: trusty
    hardware: arch=amd64 cpu-cores=1 mem=1024M availability-zone=default
    controller-member-status: has-vote

I'm using a trust image from:

  http://maas.ubuntu.com/images/ephemeral-v2/releases/

with the following bootstrap configuration:

bootstrap-timeout: 1800
enable-os-refresh-update: true
enable-os-upgrade: true
default-series: trusty
logging-config: <root>=DEBUG
lxc-clone: false
lxc-clone-aufs: false

[Andrew McDermott (frobware)]

ubuntu@node1:~$ cat /etc/cloud/build.info
build_name: server
serial: 20160311

[Andrew McDermott (frobware)]

I deployed a node via MAAS to take Juju out of the picture and I do NOT see backports listed by default:

ubuntu@node2:~$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-security main restricted universe multiverse

[Andrew McDermott (frobware)]

I switched to daily images but still do not see trusty-backports listed:

ubuntu@node3:~$ cat /etc/cloud/build.info
build_name: server
serial: 20160314

ubuntu@node3:~$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-security main restricted universe multiverse

[Andrew McDermott (frobware)]

I created a container using lxc directly on my desktop from "ubuntu 14.04 LTS amd64 (release) (20160406)".

$ lxc launch ubuntu:trusty u3

$ lxc exec u3 grep backports /etc/apt/sources.list
## Uncomment the following two lines to add software from the 'backports'
## Also, please note that software in backports WILL NOT receive any review
deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse

So the question is, which URL should I be using for MAAS

[Andrew McDermott (frobware)]

The current workaround is to:

  $ juju bootstrap ...
  $ juju ssh 0

Add:

  "deb http://archive.ubuntu.com//ubuntu trusty-backports main restricted universe multiverse"

to /etc/apt/sources.list

and run:

  $ sudo apt-get update

Drop out of the node and you can now add a container:

  $ juju add-machine lxd:0

[Andrew McDermott (frobware)]

Per IRC conversation (http://pastebin.ubuntu.com/15830771/) MAAS does not enable trusty-backports by default.

[Andrew McDermott (frobware)]

From an email conversation with Andres:

The images should have backports enabled by default, but no packages should be pulled in from it unless users actually request it. That being said, MAAS doesn't disable backports nor the images do.

This seems like a bug in the image building process, and its affecting MAAS images. See bug https://bugs.launchpad.net/uec-live-build/+bug/1513529 . I've already raised this with the CPC team and they are aware, so they'll work on fixing it.

[Robert C Jennings (rcj)]

Merged http://bazaar.launchpad.net/~ubuntu-on-ec2/vmbuilder/automated-ec2-builds/revision/723 and 14.04 images have been triggered.

[Martin Packman (gz)]

Have cloud-images in CI updated and verified this is now fixed:

<http://juju-ci.vapour.ws/job/maas-2_0-bundle-deploy/26/>

[Andrew McDermott (frobware)]

Working for me now too. Thanks.

[Andrew McDermott (frobware)]

I think this is broken again.

ubuntu@maas19-node1:~$ cat /etc/cloud/build.info
build_name: server
serial: 20160411

ubuntu@maas19-node1:~$ lsb_release -cs
trusty

ubuntu@maas19-node1:~$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-security main restricted universe multiverse

---- ^^^ I do not see backports listed ^^^ ----

ubuntu@maas19-node1:~$ sudo apt-get install lxd
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package lxd

[Dimiter Naydenov (dimitern)]

Today it's broken for me again on `MAAS Version 2.0.0 (beta5+bzr5026)`, `juju 2.0-beta8-xenial-amd64`, deploying a trusty node then switching to the controller model and adding lxd:0 failed:

2016-05-26 17:21:09 INFO juju.utils.packaging.manager utils.go:98 Retrying: &{/usr/bin/apt-get [apt-get --option=Dpkg::O
ptions::=--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
 Reading package lists...
E: The value 'trusty-backports' is invalid for APT::Default-Release as such a release is not available in the sources
 [] %!s(*syscall.SysProcAttr=<nil>) %!s(*os.Process=&{6211 0 1}) exit status 100 <nil> %!s(bool=true) [%!s(*os.File=&{0xc820980e40}) %!s(*os.File=&{0xc820980e80}) %!s(*os.File=&{0xc820980e80})] [%!s(*os.File=&{0xc820980e40}) %!s(*os.File=&{0xc820980e80})] [%!s(*os.File=&{0xc820980e60})] [%!s(func() error=0x998f60)] %!s(chan error=0xc820cb99e0)}
2016-05-26 17:21:19 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
 Reading package lists...
E: The value 'trusty-backports' is invalid for APT::Default-Release as such a release is not available in the sources
 [] %!s(*syscall.SysProcAttr=<nil>) %!s(*os.Process=&{6219 0 1}) exit status 100 <nil> %!s(bool=true) [%!s(*os.File=&{0xc820708fc0}) %!s(*os.File=&{0xc820709000}) %!s(*os.File=&{0xc820709000})] [%!s(*os.File=&{0xc820708fc0}) %!s(*os.File=&{0xc820709000})] [%!s(*os.File=&{0xc820708fe0})] [%!s(func() error=0x998f60)] %!s(chan error=0xc820a69860)}

Looking in /etc/apt/sources.list:
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-security main restricted universe multiverse

$ uname -a
Linux node-11 3.13.0-86-generic #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ cat /etc/cloud/build.info (on the MAAS node)
build_name: server
serial: 20160411

MAAS UI shows it has up-to-date images:
14.04 LTS amd64 468.8 MB 4 Thu, 26 May. 2016 19:35:21

[Dimiter Naydenov (dimitern)]

Still present on MAAS Version 2.0.0 (beta6+bzr5060) with the latest trusty image:

14.04 LTS amd64 468.8 MB 0 Fri, 03 Jun. 2016 16:45:48

(from https://images.maas.io/ephemeral-v2/releases/)

[Blake Rouse (blake-rouse)]

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...

[Andrew McDermott (frobware)]

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
> ...

[Mike Pontillo (mpontillo)]

That's weird; my `apt-cache policy lxd` shows LXD 2.0.2-0ubuntu1~16.04.1 in xenial-security/main...

[Andres Rodriguez (andreserl)]

fyi: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1513529

[Dan Watkins (oddbloke)]

This is fixed in the latest release image:

$ curl -s http://cloud-images.ubuntu.com/releases/trusty/release/ubuntu-14.04-server-cloudimg-amd64-root.tar.xz | tar OJx etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu trusty-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu trusty-security main restricted universe multiverse

[Cheryl Jennings (cherylj)]

I also verified manually on a new MAAS bootstrap. I was able to create an lxd container on top of the trusty host. Thanks, Dan!

[Andrew McDermott (frobware)]

This seems to be a problem again:

  $ juju version
  2.0-beta12-xenial-amd64

$ juju version
2.0-beta12-xenial-amd64
aim@spicy:~/kvm-maas (master)
$ juju show-machines 2
model: controller
machines:
  "2":
    juju-status:
      current: started
      since: 14 Jul 2016 12:28:20+01:00
      version: 2.0-beta12.1
    dns-name: 10.11.19.122
    instance-id: /MAAS/api/1.0/nodes/node-4447f4fc-49b5-11e6-8b89-525400b0e64b/
    machine-status:
      current: running
      message: Deployed
      since: 14 Jul 2016 12:27:48+01:00
    series: trusty

ubuntu@maas19-node6:~$ cat /etc/cloud/build.info
build_name: server
serial: 20160411

ubuntu@maas19-node6:~$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-security main restricted universe multiverse

ubuntu@maas19-node6:~$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com//ubuntu trusty main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-updates main restricted universe multiverse
deb http://archive.ubuntu.com//ubuntu trusty-security main restricted universe multiverse
ubuntu@maas19-node6:~$ sudo grep backports /var/log/juju/machine-2.log
2016-07-14 11:33:36 INFO juju.utils.packaging.manager utils.go:57 Running: apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install --target-release trusty-backports lxd
2016-07-14 11:33:36 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
2016-07-14 11:33:46 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
2016-07-14 11:33:56 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
2016-07-14 11:34:06 INFO juju.utils.packaging.manag...

[James Tunnicliffe (dooferlad)]

What a mess!

[Cheryl Jennings (cherylj)]

Andy - that's a really old image. Is that what you get when you use the released images?

[Andrew McDermott (frobware)]

My MAAS setttings has:

 http://maas.ubuntu.com/images/ephemeral-v2/releases/

and the last import date listed in the MAAS UI is/was:

 16.04 - "Thu, 14 Jul. 2016 15:18:58"

I'm prepared to reinstall my MAAS to see if it is something I have
accumulated, just not today.

On 14 July 2016 at 14:53, Cheryl Jennings <email address hidden>
wrote:

> Andy - that's a really old image. Is that what you get when you use the
> released images?
>
> --
> 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.0 on trusty
>
> Status in cloud-images:
> Invalid
> 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
> ...

[Blake Rouse (blake-rouse)]

A new trusty image is needed in releases. Promoting now.

[Cheryl Jennings (cherylj)]

Andy - you can set your image sync URL to daily to work around this: http://images.maas.io/ephemeral-v2/daily/

Andres - how often are the releases images updated for MAAS? Can the trusty one be updated since it's currently from April?

[Andrew McDermott (frobware)]

Ordinarily, yes, I am happy to use daily but I also don't want the churn. I
have enough shifting sand as it is. :)

On 14 July 2016 at 16:20, Cheryl Jennings <email address hidden>
wrote:

> Andy - you can set your image sync URL to daily to work around this:
> http://images.maas.io/ephemeral-v2/daily/
>
> Andres - how often are the releases images updated for MAAS? Can the
> trusty one be updated since it's currently from April?
>
> --
> 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.0 on trusty
>
> Status in cloud-images:
> Invalid
> Status in juju-core:
> Invalid
> Status in MAAS:
> Invalid
> Status in maas-images:
> In Progress
>
> 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
> ...

[Blake Rouse (blake-rouse)]

Image has be promoted.