With the last version of mongod, I'm seeing mongodb has exited without
being killed.
The Juju test suite assumes that it has to kill mongo during teardown and I
think checks the exit code to make sure it was juju killing mongo rather
than mongo exiting for some other reason.
The actual error log
Can't you juju upgrade-juju --upload-tools if you want to build it from
source? That only works if you only have machines that are like your build
machine, but it might be good enough for testing.
John
=:-
On Wed, Apr 8, 2015 at 4:59 PM, Mario Splivalo mario.spliv...@canonical.com
wrote:
On
On 04/08/2015 02:30 PM, Andrew Wilkins wrote:
On Wed, Apr 8, 2015 at 8:13 PM, Mario Splivalo mario.spliv...@canonical.com
wrote:
JUJU_DEV_FEATURE_FLAGS=leader-election juju upgrade-juju --upload-tools
but when I get to a previously deployed unit I don't see leader-get or
leader-set symlinks
On Wed, Apr 8, 2015 at 8:47 PM, Mario Splivalo mario.spliv...@canonical.com
wrote:
On 04/08/2015 02:30 PM, Andrew Wilkins wrote:
On Wed, Apr 8, 2015 at 8:13 PM, Mario Splivalo
mario.spliv...@canonical.com
wrote:
JUJU_DEV_FEATURE_FLAGS=leader-election juju upgrade-juju --upload-tools
On 04/08/2015 02:13 PM, Mario Splivalo wrote:
Hi!
I'm trying to test upgrade path from 1.22 to current 1.23, especially
because of leader election feature.
I know I can use that one by enabling leader-elections development flag.
I have tested that, and it works as advertised :)
But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
# juju-core 1.22.1
A new stable release of Juju, juju-core 1.22.1, is now available.
This release replaces 1.22.0.
## Getting Juju
juju-core 1.22.1 is available for vivid and backported to earlier
series in the following PPA:
