Comment 2 for bug 1391889

Revision history for this message
Edward Hope-Morley (hopem) wrote :

The following bundle:

$ cat bundle.yaml
myenv:
  services:
    ubuntu:
      charm: ubuntu
      local: trusty/ubuntu

Produces the following output:

$ juju-deployer -c bundle.yaml -d myenv
2015-06-30 22:42:00 [DEBUG] deployer.cli: Using runtime GoEnvironment on lxc
2015-06-30 22:42:00 [INFO] deployer.cli: Starting deployment of myenv
2015-06-30 22:42:00 [DEBUG] deployer.import: Getting charms...
2015-06-30 22:42:00 [ERROR] deployer.charm: Service: ubuntu has neither charm url or branch specified
2015-06-30 22:42:00 [DEBUG] deployer.deploy: Resolving configuration
2015-06-30 22:42:00 [DEBUG] deployer.env: Connecting to environment...
2015-06-30 22:42:01 [DEBUG] deployer.env: Connected to environment
2015-06-30 22:42:01 [INFO] deployer.import: Deploying services...
2015-06-30 22:42:01 [DEBUG] deployer.import: <deployer.env.go.GoEnvironment object at 0x7fa7390d0b90>
2015-06-30 22:42:01 [ERROR] deployer.charm: Service: ubuntu has neither charm url or branch specified
2015-06-30 22:42:01 [INFO] deployer.import: Deploying service ubuntu using local:trusty/ubuntu
2015-06-30 22:42:13 [DEBUG] deployer.import: Adding units...
2015-06-30 22:42:13 [DEBUG] deployer.import: Service 'ubuntu' does not need any more units added.
2015-06-30 22:42:13 [DEBUG] deployer.import: Waiting for units before adding relations
2015-06-30 22:42:14 [DEBUG] deployer.env: Delta machine: 1 change:pending
...

Note the erroneous "[ERROR] deployer.charm: Service: ubuntu has neither charm url or branch specified" which in fact gets printed for every single service deployed in this way (including subordinates) so when i have 30 odd services being de[ployed my screen fills up with ERRORs. Using locally cached charms in this way is totally legitimate so there is no need for an error or warning (or any log for that matter).