Comment 16 for bug 1746265

Was xx.xx.65.252 one of the IP addresses for machine 1? It seems odd that
the peergrouper would complain about a machine it doesn't know about.
Do these machine have multiple IP addresses? I wonder if it is a case of
somehow changing what IP addresses we are trying to assign. (In the 2.2.9
code, we're somehow selecting the first address, but 2.3.2 decided it
prefers the second address.)

How long does it take to reproduce this? Is it hours? Is it minutes?

On Wed, Feb 7, 2018 at 12:58 AM, Sandor Zeestraten <email address hidden>
wrote:

> >From #juju-dev:
>
> zeestrat> thumper: Regarding your last question in #1746265, it is a
> blocker as we haven't been able to get our controllers upgraded at all
> due to hitting this bug in our staging environment after multiple tries
> in clean environments. I can reproduce it again with some more logging
> if you'd like, but then I need to know which flags you want.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1746265
>
> Title:
> juju-upgrade from 2.2.9 to 2.3.2 fails with state changing too quickly
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1746265/+subscriptions
>