On Fri, Jul 29, 2016 at 8:27 AM, Jason Hobbs <email address hidden>
wrote:
> According to bug 1568895, an both daily and released MAAS images have
> backports enabled.
>
> ** Changed in: juju-core
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1605986
>
> Title:
> Creating container: can't get info for image 'ubuntu-trusty'
>
> Status in juju-core:
> New
>
> Bug description:
> On a deploy of OpenStack in OIL, LXD containers on one machine failed
> to be created due to this error:
>
> "Creating container: can't get info for image 'ubuntu-trusty'"
>
> Trusty container setup on other machines in the same deployment worked
> fine.
>
>
> This is with 2.0 beta 11 and 2.0 RC2.
>
> Here is the juju status:
>
> http://paste.ubuntu.com/20733843/
>
> I will attach the logs from the machine and the logs from the
> controller node.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1605986/+subscriptions
>
I verified this is the case by deploying a trusty instance in maas.
backports is enabled:
ubuntu@skookum:~$ apt-cache policy lxd ubuntu14. 04.1 0.3-0ubuntu2~ ubuntu14. 04.1 0 archive. ubuntu. com//ubuntu/ trusty- backports/ universe
lxd:
Installed: (none)
Candidate: 2.0.3-0ubuntu2~
Version table:
2.
100 http://
amd64 Packages
On Fri, Jul 29, 2016 at 8:27 AM, Jason Hobbs <email address hidden>
wrote:
> According to bug 1568895, an both daily and released MAAS images have /bugs.launchpad .net/bugs/ 1605986 paste.ubuntu. com/20733843/ /bugs.launchpad .net/juju- core/+bug/ 1605986/ +subscriptions
> backports enabled.
>
> ** Changed in: juju-core
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Creating container: can't get info for image 'ubuntu-trusty'
>
> Status in juju-core:
> New
>
> Bug description:
> On a deploy of OpenStack in OIL, LXD containers on one machine failed
> to be created due to this error:
>
> "Creating container: can't get info for image 'ubuntu-trusty'"
>
> Trusty container setup on other machines in the same deployment worked
> fine.
>
>
> This is with 2.0 beta 11 and 2.0 RC2.
>
> Here is the juju status:
>
> http://
>
> I will attach the logs from the machine and the logs from the
> controller node.
>
> To manage notifications about this bug go to:
> https:/
>