juju-deployer logs ERROR messages during successful deployment from mojo

[Thomi Richards]

There's something broken in the integration between mojo and juju-deployer.

Mojo calls juju-deployer after building a charm repository, but juju deployer logs ERROR messages about charms not being found - but the deployment succeeds. This makes it very hard to track down what actually went wrong when depoyments fail.

Here's an example:

~~~
2015-08-12 16:32:01 [INFO] Running juju-deployer
2015-08-12 16:32:01 [INFO] Running: python /usr/bin/juju-deployer -c /srv/mojo/ols-results/trusty/w5/charms/ols/mojo-ols-results/devel/services -c /srv/mojo/ols-results/trusty/w5/charms/local.cfg -s 0 -d snappy-product-integration -W -u
2015-08-12 16:32:08 [INFO] 2015-08-12 16:32:01 [DEBUG] deployer.cli: Using runtime GoEnvironment on local
2015-08-12 16:32:01 [INFO] deployer.cli: Starting deployment of snappy-product-integration
2015-08-12 16:32:01 [DEBUG] deployer.import: Getting charms...
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: haproxy has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: nrpe-external-master has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: mongodb has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: storage has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: apache2 has neither charm url or branch specified
2015-08-12 16:32:01 [DEBUG] deployer.deploy: Resolving configuration
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: haproxy has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: mongodb has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: storage has neither charm url or branch specified
2015-08-12 16:32:01 [ERROR] deployer.charm: Service: apache2 has neither charm url or branch specified
2015-08-12 16:32:01 [DEBUG] deployer.env: Connecting to environment...
2015-08-12 16:32:01 [DEBUG] deployer.env: Connected to environment
2015-08-12 16:32:01 [INFO] deployer.import: Deploying services...
2015-08-12 16:32:01 [DEBUG] deployer.import: <deployer.env.go.GoEnvironment object at 0x7f475423fad0>
2015-08-12 16:32:02 [DEBUG] deployer.import: Service 'apache2' already deployed. Skipping
2015-08-12 16:32:02 [DEBUG] deployer.import: Service 'haproxy' already deployed. Skipping
2015-08-12 16:32:02 [DEBUG] deployer.import: Service 'mongodb-storage' already deployed. Skipping
2015-08-12 16:32:02 [DEBUG] deployer.import: Service 'nrpe' already deployed. Skipping
2015-08-12 16:32:02 [DEBUG] deployer.import: Service 'spi-mongodb' already deployed. Skipping
2015-08-12 16:32:07 [DEBUG] deployer.import: Adding units...
2015-08-12 16:32:07 [DEBUG] deployer.import: Service 'apache2' does not need any more units added.
2015-08-12 16:32:07 [DEBUG] deployer.import: Service 'haproxy' does not need any more units added.
2015-08-12 16:32:07 [DEBUG] deployer.import: Service 'mongodb-storage' does not need any more units added.
2015-08-12 16:32:07 [DEBUG] deployer.import: Service 'nrpe' does not need any more units added.
2015-08-12 16:32:07 [DEBUG] deployer.import: Service 'spi-mongodb' does not need any more units added.
2015-08-12 16:32:07 [DEBUG] deployer.import: Waiting for units before adding relations
2015-08-12 16:32:07 [DEBUG] deployer.env: Connecting to environment...
2015-08-12 16:32:07 [DEBUG] deployer.env: Connected to environment
2015-08-12 16:32:07 [INFO] deployer.import: Adding relations...
2015-08-12 16:32:07 [INFO] deployer.import: Exposing service 'apache2'
2015-08-12 16:32:07 [INFO] deployer.import: Exposing service 'haproxy'
2015-08-12 16:32:08 [INFO] deployer.cli: Deployment complete in 6.48 seconds
~~~

This is really easy to reproduce: Set up a trivial mojo spec and deploy it. You don't need any particular charm or config. Feel free to reach out to me if you need help reproducing it.

[Ryan Beisner (1chb1n)]

I also consistently observe this behavior. Here is a successful mojo openstack deploy test, giving fud: "has neither charm url or branch specified"

http://paste.ubuntu.com/12065396/

juju-deployer version: 0.5.1-3
juju version: 1.24.4-0ubuntu1~14.04.1~juju
mojo version: 0.1.12

Tripping @:
http://bazaar.launchpad.net/~juju-deployers/juju-deployer/trunk/view/head:/deployer/charm.py#L89

[Tim Van Steenburgh (tvansteenburgh)]

Duplicate of https://bugs.launchpad.net/juju-deployer/+bug/1391889 (fixed)