Canonical Juju

  1. Bug #1657831
  2. Comment #9

Comment 9 for bug 1657831

Revision history for this message
John A Meinel (jameinel) wrote :

So I think there are several things going on:

If you look at machine-2.log from 'logs2.tar.gz' you see this line:
2017-01-18 21:03:36 WARNING juju.provisioner lxd-broker.go:62 failed to prepare container "2/lxd/2" network config: linking device interface "eth0" to subnet "10.245.0.0/18" failed: unexpected: ServerError: 504 GATEWAY TIMEOUT (Unexpected exception: TimeoutError. See /var/log/maas/regiond.log on the region server for more information.)
2017-01-18 21:03:36 WARNING juju.provisioner broker.go:97 incomplete DNS config found, discovering host's DNS config

I don't know why MAAS gave a 504 Gateway Timeout.

Juju will attempt to retry these type of failures, but can run into bug #1670873 (fixed in 2.1.2 whenever that gets released). The specific behavior of falling back to LXDBR0 based addresses is bug #1656326 which should already be fixed in the Juju 2.1.1 release.

So I'm reasonably ok treating this as just a dupe of bug #1656326 with the caveat that whatever the specific error is that is giving us 504 trying to talk to MAAS is an unknown bug. (But probably not worthy of keeping *this* bug open.)