Mongo version problem hangs tests
Bug #1097556 reported by
Jeroen T. Vermeulen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
This appears to be a known problem and it's preventing us from running the tests, so I'm filing a bug for it. Others will know more about it though.
Apparently the test suite tries to start mongo with some command-line option that the versions currently in Ubuntu don't support. That doesn't work, and the test framework just waits (almost) forever and then times out the test.
Martin is adding something to the README about this, but it's still vague and none of us know what or where the "mongo public bucket" is. How do we get a mongodb that will work with juju-core?
Related branches
lp://staging/~axwalk/juju-core/lp1097556-mongod-failure-hangs-tests
- Juju Engineering: Pending requested
-
Diff: 22 lines (+5/-0)1 file modifiedtesting/mgo.go (+5/-0)
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | none → 1.14.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Yes, the tests assume mongo 2.2.0+TLS is in your path as mongod, but this version is not shipped with Precise or Quantal.
http:// juju-dist. s3.amazonaws. com/tools/ mongo-2. 2.0-$SERIES- amd64.tgz