Comment 27 for bug 1519527

On Thu, Nov 26, 2015 at 10:17 AM, Dimiter Naydenov <
<email address hidden>> wrote:

> Andreas, Juju is catching any errors from claim-sticky-ip-address. At
> TRACE level each relevant MAAS API call response is logged regardless of
> outcome. On a successful claim-sticky-ip-address response, there should
> be a INFO level log like this:
>
> INFO juju.provider.maas environ.go:1564 reserved sticky IP address for
> device "node-dfa45ca0-92f5-11e5-8cca-d4bed9a84493" representing
> container "juju-machine-0-lxc-0"
>
> That should appear shortly after the device creation, logged as:
>
> INFO juju.provider.maas environ.go:1543 created device "node-
> dfa45ca0-92f5-11e5-8cca-d4bed9a84493" for container "juju-
> machine-0-lxc-0" with MAC address "00:16:3e:fb:06:d7" on parent node
> "/MAAS/api/1.0/nodes/node-d4692494-8228-11e4-8078-d4bed9a84493/"
>
> I can't see the "reserved sticky.." log anywhere, which is weird, so I
> investigated some more.
>
> Looking at how the code is implemented, I can now confirm errors from
> claim-sticky-ip-address are effectively ignored further up the stack.
> I've filed another bug #1520199 about this, as Juju can do better - in
> fact the the absence of an IP address in the response should be caught
> and reported as error. But, that won't solve the current issue with
> MAAS misbehaving.
>

Thanks. At least maas told juju it was misbehaving ;)