Comment 2 for bug 1700731

I can see the folder holding the log file, but I'm unable to download the
log file itself.

Can you tell us what cloud this is? Offhand I would expect this to be an
issue of restarting the controller, not because of running mgopurge.

The spaces discovery worker in 2.1.3 runs at startup (and clearly is
bouncing due to being unhappy about this particular issue). In 2.2 it only
runs on initial bootstrap or add-model or when triggered by the user (juju
reload-spaces).

One question is if a given subnet CIDR has been removed and then added
again. Which might cause us to error with a conflict.

So the particular 'worker is erroring over and over in the log file' should
be fixed in 2.2, but the actual "handle when subnets are removed and
re-added" is probably not.

On Tue, Jun 27, 2017 at 8:30 PM, Peter Sabaini <email address hidden>
wrote:

> I've uploaded machine-0 log here: https://private-
> fileshare.canonical.com/~sabaini/Lo4ahl2xohk3quoo/lp1700731/
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1700731
>
> Title:
> ERROR log from space-importer after mgopurge
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1700731/+subscriptions
>