juju test suite should use juju-mongodb
Bug #1301353 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Low
|
John A Meinel | ||
1.18 |
Fix Released
|
Low
|
John A Meinel |
Bug Description
When using juju on trusty we now use juju-mongodb to provide "mongod". However, for testing purposes we still require "mongod" to be on the PATH and we give ugly panics when it isn't available.
installing 'mongodb-server' works around the issue for now, but the test suite should be able to use our preferred mongo on trusty.
Related branches
lp:~waigani/juju-core/1301353-mongodb-dep
- Juju Engineering: Pending requested
-
Diff: 337 lines (+14/-200)3 files modifiedMakefile (+1/-1)
provider/local/prereqs.go (+10/-104)
provider/local/prereqs_test.go (+3/-95)
lp:~jameinel/juju-core/1.18-trusty-mongodb-1301353
- Juju Engineering: Pending requested
-
Diff: 86 lines (+37/-7)2 files modifiedstore/mgo_test.go (+21/-4)
testing/mgo.go (+16/-3)
lp:~jameinel/juju-core/use-juju-mongodb-1301353
- Juju Engineering: Pending requested
-
Diff: 98 lines (+31/-9)2 files modifiedstore/store_test.go (+1/-1)
testing/mgo.go (+30/-8)
Changed in juju-core: | |
assignee: | nobody → Jesse Meek (waigani) |
milestone: | none → 2.0 |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | 2.0 → 1.19.0 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core: | |
assignee: | nobody → John A Meinel (jameinel) |
milestone: | none → 1.19.2 |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The fix from Jesse was not actually related to *this* bug. This bug is the fact that if you are on Trusty and have "juju-mongodb" installed (say via juju-local), the test suite still fails because it is looking for "mongod" to be in $PATH. juju/bin/ mongod if it cannot find mongod in $PATH.
We shouldn't have to add a symlink for the test suite to run (or install mongodb-server). Instead, it should use /usr/lib/
I still want to prefer mongod in $PATH because the charm store tests need the v8 engine that is not available in juju-mongodb.