Comment 1 for bug 1668359

This is the actual bug:
2017-02-27 17:55:46 WARNING juju.provisioner lxd-broker.go:82 failed to
prepare container "0/lxd/0" network config: unable to look up
static-routes: unexpected: ServerError: 404 NOT FOUND (Unknown API
endpoint: /MAAS/api/2.0/static-routes/.)

I had previously consulted the MAAS API docs:
https://docs.ubuntu.com/maas/2.0/en/api#static-route

Which looked like MAAS 2.0 indeed had the API exposed.

I had previously had code that would have handled missing static-routes
more gracefully, but in review it came up that it didn't seem right to
suppress the error, and the info *I* had on hand looked like MAAS 2.0 was
supposed to support it.

John
=:->

On Mon, Feb 27, 2017 at 10:25 PM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> Curtis Hovey (sinzui) has assigned this bug to you for juju:
>
> As seen at
> http://reports.vapour.ws/releases/issue/585c1726749a567a6807af2a
>
> As of 2017--2-27, the juju ssh 0/lxd/1 ip route show fails quickly in
> juju 2.1 on maas 2.0 only starting with
> http://reports.vapour.ws/releases/4936
> https://github.com/juju/juju/commit/5a819de83cfecfefd0fba221633fdf
> 929efdba76
>
>
> This is the recent static route support change.
>
> The previous Bug #1652130 shown in the issue was fixed.
>
> ** Affects: juju
> Importance: Critical
> Assignee: John A Meinel (jameinel)
> Status: Triaged
>
>
> ** Tags: ci lxd maas-provider network regression
> --
> Container routing busted in maas 2.0 juju 2.1
> https://bugs.launchpad.net/bugs/1668359
> You received this bug notification because you are a bug assignee.
>