Comment 2 for bug 1717590

Liam,

I tested again without telegraf and didn't hit this issue - hacluster-pxc
was able to come up on its own without any intervention in a reasonable
amount of time - about 90 minutes after the deploy started, where before it
was hitting a 4 hour time limit and failing.

Jason

On Mon, Sep 18, 2017 at 4:03 AM, Liam Young <email address hidden>
wrote:

> Hi Jason.
> To narrow down the issue would it be possible to test without telegraf
> ? Looking at the mysql hook executions from your pastebin I see ~60
> telegraf units with relation to mysql ( http://paste.ubuntu.com/25563847/
> )
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1717590
>
> Title:
> percona-cluster unit constantly fires hooks, blocks hacluster unit
> from being setup
>
> Status in OpenStack percona-cluster charm:
> New
>
> Bug description:
> juju version: 2.2.4
> percona-cluster charm: cs:percona-cluster-254
>
> =Description=
> This is a bundle using percona-cluster and hacluster:
> http://paste.ubuntu.com/25542493/
>
> It gets stuck, so far for about an hour, in a state where hacluster-pxc
> is not setup because the hacluster unit on the mysql/0 host never gets to
> run its hooks to setup:
> http://paste.ubuntu.com/25542486/
>
> The mysql/0 unit continuously fires, here's the log for it:
> http://paste.ubuntu.com/25542506/
>
> =To Reproduce=
> Deploy the bundle shown above. I don't know for sure if it happens
> everytime yet.
>
> =Partial Workaround=
> I have been able to workaround this for a manual deployment by stopping
> the jujud-unit-mysql-0 service, letting the hacluster charm do its thing,
> then restarting the service. Unfortunately, this is difficult to automate.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charm-percona-cluster/+bug/
> 1717590/+subscriptions
>