Deployment failure
William Reade
william.reade at canonical.com
Wed Sep 26 07:11:36 UTC 2012
On Wed, 2012-09-26 at 17:00 +1000, David Cheney wrote:
> lucky(~/src/launchpad.net/juju-core/cmd/juju) % juju bootstrap --upload-tools --debug
> 2012/09/26 16:54:54 JUJU environs/ec2: opening environment "us-east-1"
> 2012/09/26 16:54:54 JUJU environs/ec2: bootstrapping environment "us-east-1"
> juju deploy mongodb
> juju deploy 2012/09/26 16:55:03 JUJU environs: putting tools tools/juju-0.0.1-precise-amd64.tgz (3552kB)
> mysql
> 2012/09/26 16:55:51 JUJU environs/ec2: starting machine 0 in "us-east-1" running tools version "0.0.1-precise-amd64" from "https://s3.amazonaws.com/juju-4218c46225cb7856d9d5ca3c1a685cd87b647996/tools/juju-0.0.1-precise-amd64.tgz?AWSAccessKeyId=AKIAJ4SOKUWG25EDMAOA&Expires=1380178551&Signature=HrW7jIlqa0Hr7F0rJ0oAwCAbBcU%3D"
> 2012/09/26 16:55:56 JUJU environs/ec2: started instance "i-db41bfa6"
> lucky(~/src/launchpad.net/juju-core/cmd/juju) % juju deploy mongodb
> error: cannot assign unit "mongodb/0" to machine: cannot assign unit "mongodb/0" to machine 1: duplicate key insert for unique index of capped collection
Sorry, cannot repro myself :(.
>
> How did this happen ?
>
>
>
More information about the Juju-dev
mailing list