Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

[Curtis Hovey-Canonical]

On Tue, May 17, 2016 at 4:22 AM, David Cheney
<david.cheney at canonical.com> wrote:
> What is the story with mongo ? It's constantly causing builds to fail
> CI because of it's complete shitness.
>
> I've heard that some people have moved to mongo 3.2 which fixes the
> problem, but as CI clearly is running the old rubbish version, this
> clearly isn't a problem which can be called fixed.

Ci runs the juju unit tests as specified by the juju makefile. eg
    make install-deps
    make test

^ I don't see mongodb3.2 in the make file. Their rules actually call
for juju-mongodb or mongodb-server. Someone can easily fix their
makefile. I made changes recently to support lxd and the golang 1.6
compiler used by ppc64el, arm64 and s390x.

There are cases where the makefile doesn't work, such as windows and
centos. We manually installed mongo on the hosts. We can put a card on
the board to change the mongo versions if Cheryl and Alexis want.
Note, that centos and windows don't host mongo in real life, so
something is wrong if the test suite requires a controller run on an
unsupported OS.

> What is the solution ? Will mongo 2.6 be deprecated entirely and the
> build fail it the mongo version installed is < 3.2 ?

The juju-mongo2.6 package will be be preferred by juju 1.2.5 in xenial
and without other changes, 2.4 will be used by all other 1.25 series.

Precise wont ever have juju-mongodb3.2 (and it does not use
juju-mongodb2.4 either). Nor will wily in it remaining two months.
Trusty will get juju-mongodb3.2 soon. We have two packaging changed
queued for yakkety before we can begin the backports to xenial and
trusty.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui