Comment 10 for bug 1303787

Sure, can you please provide the rest of the information. I'd be
surprised if 1.17 -> 1.18 had any impact on the frequency of this bug.

On Tue, Apr 8, 2014 at 10:00 AM, Tim Van Steenburgh
<email address hidden> wrote:
> Ugh, sorry Dave, but since the original bug report, juju has been
> upgraded on wolfe-01 to 1.18. I don't know what the original versions
> were, except that juju was 1.17.7.
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1303787
>
> Title:
> hook failures - nil pointer dereference
>
> Status in juju-core:
> Incomplete
>
> Bug description:
> I deployed the following on wolfe-01 (ppc64el) using the local
> provider:
>
> The charms used:
>
> parent branch: bzr+ssh://bazaar.launchpad.net/~charmers/charms/precise/haproxy/trunk/
> parent branch: bzr+ssh://bazaar.launchpad.net/~charmers/charms/precise/memcached/trunk/
> parent branch: bzr+ssh://bazaar.launchpad.net/~mbruzek/charms/trusty/mysql/apache2fix/
> parent branch: bzr+ssh://bazaar.launchpad.net/~cabs-team/charms/trusty/sugarcrm/trunk/
>
> The deploy script:
>
> juju deploy local:trusty/sugarcrm
> juju deploy local:trusty/mysql
> juju deploy local:trusty/memcached
> juju deploy local:trusty/haproxy
> juju set mysql dataset-size="1G"
> juju add-relation sugarcrm mysql
> juju add-relation sugarcrm memcached
> juju add-relation sugarcrm haproxy
> juju expose haproxy
>
> I waited for all services to start up successfully, and they did.
>
> Fast-forward 7 hours, I log in to wolfe-01 and this is the juju status:
> http://paste.ubuntu.com/7216852/
>
> I've attached the all-machines.log, which contains nil pointer errors.
>
> Unfortunately, I can't be sure what transpired on the machine during
> those 7 hours - only that I didn't touch anything.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1303787/+subscriptions