Invalid --to parameter

Bug #1638685 reported by Seman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-deployer
Incomplete
Low
Tim Van Steenburgh

Bug Description

When deploying this bundle https://api.jujucharms.com/charmstore/v5/~juju-qa/ceph-with-dash-3/archive/ceph-with-dash-lxd.yaml, the deployer generates invalid juju command:

2016-11-01 11:27:05 [DEBUG] deployer.env: Connecting to cwr-maas-power8:cwr-maas-power8...
2016-11-01 11:27:06 [DEBUG] deployer.env: Connected.
2016-11-01 11:27:06 [INFO] deployer.import: Creating machines...
2016-11-01 11:27:06 [INFO] deployer.import: Machine 0 will be created
2016-11-01 11:27:06 [INFO] deployer.import: Deploying applications...
2016-11-01 11:27:06 [INFO] deployer.import: Deploying application ceph-collector using cs:~canonical-storage/xenial/ceph-collector-4
2016-11-01 11:27:06 [DEBUG] deployer.import: Refetching status for placement deploys
2016-11-01 11:27:15 [DEBUG] deployer.import: Setting annotations
2016-11-01 11:27:15 [INFO] deployer.import: Deploying application ceph-dash using cs:~canonical-storage/xenial/ceph-dash-11
2016-11-01 11:27:15 [DEBUG] deployer.import: Refetching status for placement deploys
2016-11-01 11:27:20 [ERROR] deployer.env: Error deploying application 'ceph-dash'
2016-11-01 11:27:20 [ERROR] deployer.env: Command (juju deploy -m cwr-maas-power8:cwr-maas-power8 --to=lxd: --series xenial cs:~canonical-storage/xenial/ceph-dash-11 ceph-dash) Output:

 error: invalid --to parameter "lxd:"

2016-11-01 11:27:20 [INFO] deployer.cli: Deployment stopped. run time: 14.98

Revision history for this message
Seman (sseman) wrote :

juju 2.0.0
juju-deployer (0.9.2)
jujubundlelib (0.5.2)
jujuclient (0.53.3)

Revision history for this message
Tim Van Steenburgh (tvansteenburgh) wrote :

Using the latest juju-deployer, I deployed this bundle on aws via:

$ cd /tmp
$ wget https://api.jujucharms.com/charmstore/v5/~juju-qa/ceph-with-dash-3/archive/ceph-with-dash-lxd.yaml
$ juju-deployer -Wvd -c ceph-with-dash-lxd.yaml

The deployment completed successfully, with no errors.

Are you deploying the bundle directly with juju-deployer, or indirectly, with another tool? Is there any chance the bundle is being modified before being passed to juju-deployer?

Changed in juju-deployer:
assignee: nobody → Tim Van Steenburgh (tvansteenburgh)
status: New → Incomplete
Revision history for this message
Seman (sseman) wrote :

This was deployed using the Bundletester. I will open a bug against the BT.

Revision history for this message
Seman (sseman) wrote :
Tom Haddon (mthaddon)
Changed in juju-deployer:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.