Mongo: SetUpTest/TearDownTest no reachable servers

[Curtis Hovey]

As seen in
    http://reports.vapour.ws/releases/issue/57bcbea5749a561a5ee6abe2

MachineSuite.TearDownTest no reachable servers. Since teardown is bringing down mongodb, we might consider this a success and move on.

/home/ubuntu/juju-core_2.0-beta7/src/github.com/juju/juju/provider/dummy/environs.go:308:
    c.Assert(err, jc.ErrorIsNil)
... value *errors.Err = &errors.Err{message:"inst.Dial() failed", cause:(*errors.errorString)(0xc82083f6f0), previous:(*errors.errorString)(0xc82083f6f0), file:"github.com/juju/testing/mgo.go", line:494} ("inst.Dial() failed: no reachable servers")

[Anastasia (anastasia-macmood)]

Linked report tell me "USE ME, NO BUG LINKED" \o/

Is this still a failure?

[Aaron Bentley (abentley)]

I've updated to the correct link.

[Tim Penhey (thumper)]

I think this may be fixed by the PR that fixes bug 1455627

[Curtis Hovey (sinzui)]

Sorry, this issue is still being seen as of Sep 20.

[Reed O'Brien (reedobrien)]

There is now a patch in the patches directory that will -- with any luck -- eliminate a bunch of these failures. Certainly the data race in mgo and hopefully a number of others as a side effect.

Refs: https://bugs.launchpad.net/juju/+bug/1604817
Refs: https://github.com/juju/juju/commit/359b16bf8a0bd3f379ac0be133b70a965c51ca1e

[Reed O'Brien (reedobrien)]

We were working on this at the sprint in London, but currently not looking at it. Transitioned back to triaged.

[Anastasia (anastasia-macmood)]

Most recent occurrence as of 30-May-2018: http://ci.jujucharms.com/job/github-merge-juju/549/console

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.