Mongo error when deploying charm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
High
|
Dimiter Naydenov |
Bug Description
When deploying a charm from a newly launched Juju GUI I get the following notification:
Error deploying mediawiki
Could not deploy the requested service. Server responded with: cannot add charm "cs:precise/
This happens using an ec2 environment booted using juju-quickstart with juju locally built from revision 2282. It was a test for Dimiter's fix for bug 1067979.
With the same environment, an attempt to deploy a service via the command-line worked. Subsequent charm deploys from the GUI also worked, including a deploy of mediawiki.
Previous instances of this bug (running locally) showed multiple charm deploys failing for a variety of different charms. That was with the PPA version 1.17.1-
description: | updated |
Changed in juju-core: | |
assignee: | nobody → Dimiter Naydenov (dimitern) |
description: | updated |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: deploy race-condition |
I tried the following on the latest trunk (r2285):
juju bootstrap --upload-tools
juju deploy juju-gui --to 0
juju expose juju-gui
And then from the GUI I deployed 1 mediawiki unit. I was watching the websocket log in Chrome's network tab and the JS console. I couldn't see any errors. All services came up OK and no errors were reported.
I'm not sure what's juju-quickstart, so I haven't used it.
Anyway - any clue as to how to reproduce it? Remember, when using --upload-tools from source you'll need to rebuild the binaries from source first. I use the following script for that:
#!/bin/bash
pushd /home/dimitern/ work/juju- core/
cd cmd/juju && go install . && cd ../jujud && go install .
ls -la `which juju`
ls -la `which jujud`
popd