Comment 21 for bug 1412621

Absolutely correct
Thanks

On Wed, Oct 21, 2015 at 9:45 PM, Cheryl Jennings <
<email address hidden>> wrote:

> This problem seems to show up the first time a particular node in a MAAS
> is selected for the bootstrap node. I hit this consistently with the
> following steps:
>
> 1 - juju bootstrap (chosen MAAS node is node0, for example)
> 2 - bootstrap fails with the above EMPTYCONFIG error
> 3 - juju destroy-environment --force (won't work without --force)
> 4 - juju bootstrap (will succeed if chosen MAAS node is node0)
>
> If I then destroy the environment and then force a different node to be
> chosen as the bootstrap node, I see the same error again.
>
> Here is the log from the failed bootstrap:
> http://paste.ubuntu.com/12887244/
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1508498).
> https://bugs.launchpad.net/bugs/1412621
>
> Title:
> replica set EMPTYCONFIG MAAS bootstrap
>
> Status in juju-core:
> Triaged
> Status in juju-core 1.24 series:
> Triaged
>
> Bug description:
> When attempting to bootstrap juju during a new stack deploy, it failed
> with the following error message:
>
> 2015-01-19 06:16:39 WARNING juju.replicaset replicaset.go:87 Initiate:
> fetching replication status failed: cannot get replica set status:
> can't get local.system.replset config from self or any seed
> (EMPTYCONFIG)
>
> Complete log of the deploy attempt is attached.
>
> When the juju bootstrap was attempted manually using the same command,
> it succeeded; this suggests there might be a race condition in the
> bootstrap process.
>
> This may be a duplicate of https://bugs.launchpad.net/juju-
> core/+bug/1384549, but the symptoms are different.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1412621/+subscriptions
>