Comment 3 for bug 1271937

On Wed, Mar 5, 2014 at 6:32 AM, Curtis Hovey <email address hidden> wrote:
> juju-mongodb is partially enabled in 1.17.4 The db is used when it is
> present on the host. Juju will install the wrong db (mongodb-server)
> when left to it's own devices.

Does that imply a workaround? If so, I'd be interested so I could
continue to make progress.

To be clear, the specific issue I'm seeing is that the 1.17.4
bootstrap code seems to fail if it cannot install mongodb-server on
the bootstrap node.
This works fine on x86 since it *can* install mongodb-server. But, if
I hack the code to c.AddPackage("juju-mongodb") instead, bootstrapping
using a trusty/amd64 image begins to fail (see below). I'm guessing
there's more code needed to startup and configure this alternate
server.

$ juju bootstrap
Launching instance
 - i-6dd2eb4c
Waiting for address
Attempting to connect to ec2-184-73-95-66.compute-1.amazonaws.com:22
Attempting to connect to ip-10-178-35-82.ec2.internal:22
Attempting to connect to 184.73.95.66:22
Attempting to connect to 10.178.35.82:22
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: git
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: juju-mongodb
Fetching tools: curl -o $bin/tools.tar.gz
'https://juju-dist.s3.amazonaws.com/tools/releases/juju-1.17.4-trusty-amd64.tgz'
Starting MongoDB server (juju-db)
Bootstrapping Juju machine agent
ERROR bootstrap failed: rc: 1
Stopping instance...
ERROR rc: 1