ERROR TLS handshake failed: EOF waiting for stateserver

[Aaron Bentley]

After running "juju bootstrap", the next command emits "ERROR TLS handshake failed: EOF" repeatedly until the stateserver is ready. After the stateserver is ready, it no longer emits this error.

Since failure to connect is expected, this error should not be shown.

Seen with juju 1.16.0-saucy-amd64

[Curtis Hovey (sinzui)]

From the duplicate:
this happends during bootstrap and, i believe this is why MaaS does not report to juju that the bootstrap node is ready?

this repeats it self every second until environments is destroy..

juju handshake node error..why (juju.state open.g:93 TLS handshake failed: x509:certificate has expired or is not yet valid

[juan c caballero (juancc2007)]

this also happens in juju core version 1.16.3-precise-amd64

[juan c caballero (juancc2007)]

this may be a cloud init problem when initializing the juju node for juju use , something in the cloud init software that get loaded or does not get loaded.

[John A Meinel (jameinel)]

I believe this doesn't happen in 1.18+

On Sat, May 31, 2014 at 5:26 PM, juan c caballero <email address hidden>
wrote:

> this may be a cloud init problem when initializing the juju node for
> juju use , something in the cloud init software that get loaded or does
> not get loaded.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1245550
>
> Title:
> ERROR TLS handshake failed: EOF waiting for stateserver
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1245550/+subscriptions
>

[juan c caballero (juancc2007)]

thanks, i have upgraded errors are gone. but now i get nothing. just cloud
init ready. on the node. and no juju status, no available nodes.
nothing...maas is still not telling juju that the node is ready for juju,
now confirmed in 1.18.4-precise-amd64, none VM

On Tue, Jun 3, 2014 at 8:33 AM, John A Meinel <email address hidden>
wrote:

> I believe this doesn't happen in 1.18+
>
>
> On Sat, May 31, 2014 at 5:26 PM, juan c caballero <email address hidden>
> wrote:
>
> > this may be a cloud init problem when initializing the juju node for
> > juju use , something in the cloud init software that get loaded or does
> > not get loaded.
> >
> > --
> > You received this bug notification because you are subscribed to juju-
> > core.
> > https://bugs.launchpad.net/bugs/1245550
> >
> > Title:
> > ERROR TLS handshake failed: EOF waiting for stateserver
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/juju-core/+bug/1245550/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1324331).
> https://bugs.launchpad.net/bugs/1245550
>
> Title:
> ERROR TLS handshake failed: EOF waiting for stateserver
>
> Status in juju-core:
> Triaged
>
> Bug description:
> After running "juju bootstrap", the next command emits "ERROR TLS
> handshake failed: EOF" repeatedly until the stateserver is ready.
> After the stateserver is ready, it no longer emits this error.
>
> Since failure to connect is expected, this error should not be shown.
>
> Seen with juju 1.16.0-saucy-amd64
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1245550/+subscriptions
>