Unable to bootstrap local provider, missing juju-mongodb dependency
Bug #1295609 reported by
Stuart Bishop
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Critical
|
Curtis Hovey | ||
Bug Description
I am unable to bootstrap 1.17.6 with the local provider, hanging for longer than I'm prepared to wait. This is a regression from 1.17.5.
/var/log/
/bin/sh: 1: exec: /usr/lib/
Manually installing the juju-mongodb package fixes the issue.
| Changed in juju-core: | |
| milestone: | none → 1.17.7 |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| tags: | added: mongodb packaging |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → Curtis Hovey (sinzui) |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
@James.
I changed local packaging to
juju-mongodb | mongodb-server
under the assumption that we want to keep the older mongodb for existing envs. The release notes suggests trusty users manually install juju-mongodb *if* they was to bootstrap with it. It appears juju *requires* it for trusty. I think we need separate packaging for trusty that only depends on juju-mongodb.