Comment 6 for bug 1942804

On Wed, Feb 22, 2023 at 03:53:19PM -0000, John A Meinel wrote:
> So I think the original issue isn't about Fan addresses in the delay on coming back up. Specifically we see this line:
>
> | 2021-09-09 08:41:11 ERROR juju.worker.dependency engine.go:671 "migration-minion" manifold worker returned unexpected error: txn watcher sync error
> | 2021-09-09 08:41:11 ERROR juju.worker.dependency engine.go:671 "log-sender" manifold worker returned unexpected error: cannot send log message: websocket: close sent
>
> Which is fairly clearly indicating that the controller itself just died
> with a 'txn watcher sync error' which generally is a hard restart of a
> lot of the controller internals. (essentially we lost sync with the
> database, so we start over to make sure that our current state is back
> in sync).
>
> I wouldn't be surprised if it actually really did take 60s for the controller to come back up, and in that time it was just a while before the genuine ports of 10.131.4.170:17070 or 10.131.4.109:17070 became available.
> We actually try multiple addresses simultaneously (because we are also trying .170 as well as .109 at the same time), and it happens that the fan addresses fail faster than the real addresses which is why you see the messages in the logs.
>

Oh! Thank you for the explanation here. This is highly likely it and
the logging being just noise then.