Hi Mark & Cheryl,
I have posted a comment to the bug report page and attached all logs to it.
You can check it to see what's happened in other machines when Juju
bootstrap server failed in my environment.
Many thanks for your help.
Sincerely yours,
Leon
On Wed, Oct 28, 2015 at 2:26 AM, Cheryl
Hi Leon,
I was able to recreate the "lost" agent in a simple environment and have
opened up a bug for it: https://bugs.launchpad.net/juju-core/+bug/1510651
Since my environment was pretty simple, I didn't run into any hook errors.
Could you attach the unit logs from some of the services with err
Thanks for following up!
We will take a look at the logs and get back to you soon.
--Mark Ramm
On Mon, Oct 26, 2015 at 4:41 AM, 曾建銘 wrote:
> Hi Mark & Marco,
>
> Really appreciate your help. I have already provide the logs to Marco.
>
> Hope it could help you to enhance the Juju HA feature.
>
Hi Mark & Marco,
Really appreciate your help. I have already provide the logs to Marco.
Hope it could help you to enhance the Juju HA feature.
Sincerely yours,
Leon
On Sat, Oct 24, 2015 at 7:03 AM, Mark Shuttleworth wrote:
> On 23/10/15 00:54, 曾建銘 wrote:
> > Was the juju doing something for f
On 23/10/15 00:54, 曾建銘 wrote:
> Was the juju doing something for fixing specific problem? I think that
> service on failed node should only become lost and not interfere services
> on workings nodes. But it didn't act as I expected.
>
> By the way, I used Juju to deploy OpenStack, so I deployed a l
Hi Marco,
Many thanks for your reply, the juju version I used is 1.24.6-trusty-amd64.
I found that when a juju node failed, not only the services on the node
change to lost, but alse services on other working nodes change to
executing or even error.
I tried to log into the other working node and
Hi Leon,
Sorry to hear you're having issues, I haven't seen this problem before but
I'm curious what version of Juju you're using (`juju version`) I know there
was recent work to make ensure-availability more robust. As to how to solve
the issue, could you run `juju ssh 0` then once on the zero no
Hi All,
I got some problems when I was testing Juju High Availability after
deploying OpenStack on my physical servers.
I used "juju ensure-availability" to generate 3 state servers. Juju became
unnormal after the bootstrap node was shutdown.
When the bootstrap node was gone, the whole juju task