local provider should be updated to reflect juju only mongodb server

[Dave Cheney]

$ juju bootstrap -v
verbose is deprecated with the current meaning, use show-log
2014-02-07 01:32:45 INFO juju.provider.local environprovider.go:77 checking state port
2014-02-07 01:32:45 INFO juju.provider.local environprovider.go:77 checking API port
2014-02-07 01:32:45 INFO juju.provider.local environprovider.go:35 opening environment "local"
2014-02-07 01:32:46 ERROR juju.provider.local environprovider.go:51 failed verification of local provider prerequisites: stat /usr/bin/mongod: no such file or directory
MongoDB server must be installed to enable the local provider:

    sudo apt-get install mongodb-server
2014-02-07 01:32:46 ERROR juju.cmd supercommand.go:294 stat /usr/bin/mongod: no such file or directory
MongoDB server must be installed to enable the local provider:

    sudo apt-get install mongodb-server

These instructions are incorrect, the recommended package is 'juju-mongodb', however when this is installed juju still refuses to start

[Antonio Rosales (arosales)]

Juju needs knowledge of juju-mongo-db binary location.

-thanks,
Antonio

[Antonio Rosales (arosales)]

Chatting with James Page Juju would need a method to detect if Juju is running on Trusty or if the package is available and then take the correct action. Specifically, if on Trusty or if the juju-mongo-db package is available update Juju's upstart script to use the juju-mongo-db binary location, which is intentionally different than the default mongo location.

-thanks,
Antonio

[Martin Packman (gz)]

Progress towards this was landed, but has been partially backed out due to bug 1286279.

[Anastasia (anastasia-macmood)]

With several upgrades to different mongo versions, there have been a lot changes in the area on both Juju 1.25 and 2.0 since this bug has been last commented on.

We believe that this has been resolved as part of the ongoing development. If you see otherwise when running Juju 2, please file a new bug against "juju" project.