add-machine method Client.AddMachinesV2 is not implemented
Bug #1317267 reported by
Curtis Hovey
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
This command works with juju 1.18.2 client talking to a 1.18.2 state-server
juju --debug add-machine ssh:ubuntu@
But it fails when the client is 1.19.1
ERROR juju.cmd supercommand.go:304 no such request - method Client.
I it appears that devel is not compatible with stable.
Related branches
lp:~axwalk/juju-core/lp1317267-manual-addmachine1dot18
- Juju Engineering: Pending requested
-
Diff: 15 lines (+4/-1)1 file modifiedenvirons/manual/provisioner.go (+4/-1)
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The failure looks like
juju --debug add-machine ssh:ubuntu@ 10.55.32. 174 19.1-trusty- amd64 [gc] 84-244- 38.compute- 1.amazonaws. com:17070] ec2-54- 84-244- 38.compute- 1.amazonaws. com:17070/ " ec2-54- 84-244- 38.compute- 1.amazonaws. com:17070/ " manual init.go:139 initialising "10.55.32.174", user "ubuntu" hecking no" -o "PasswordAuthen tication no" -i /home/curtis/ Work/juju- qa/ssh/ juju_id_ rsa -i /home/curtis/ .ssh/id_ rsa ubuntu@10.55.32.174 sudo -n true manual init.go:150 ubuntu user is already initialised manual init.go:38 Checking if 10.55.32.174 is already provisioned hecking no" -o "PasswordAuthen tication no" -i /home/curtis/ Work/juju- qa/ssh/ juju_id_ rsa -i /home/curtis/ .ssh/id_ rsa ubuntu@10.55.32.174 /bin/bash manual init.go:55 10.55.32.174 is not provisioned manual init.go:67 Detecting series and characteristics on 10.55.32.174 hecking no" -o "PasswordAuthen tication no" -i /home/curtis/ Work/juju- qa/ssh/ juju_id_ rsa -i /home/curtis/ .ssh/id_ rsa ubuntu@10.55.32.174 /bin/bash manual init.go:120 series: precise, characteristics: arch=amd64 cpu-cores=1 mem=995M AddMachinesV2 is not implemented
2014-05-07 18:26:38 INFO juju.cmd supercommand.go:301 running juju-1.
2014-05-07 18:26:38 DEBUG juju.conn api.go:185 trying cached API connection settings
2014-05-07 18:26:38 INFO juju.conn api.go:268 connecting to API addresses: [ec2-54-
2014-05-07 18:26:38 INFO juju.state.api apiclient.go:198 dialing "wss://
2014-05-07 18:26:39 INFO juju.state.api apiclient.go:144 connection established to "wss://
2014-05-07 18:26:39 INFO juju.environs.
2014-05-07 18:26:39 DEBUG juju.utils.ssh ssh.go:234 using OpenSSH ssh client
2014-05-07 18:26:39 DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh -o "StrictHostKeyC
2014-05-07 18:26:40 INFO juju.environs.
2014-05-07 18:26:40 INFO juju.environs.
2014-05-07 18:26:40 DEBUG juju.utils.ssh ssh.go:234 using OpenSSH ssh client
2014-05-07 18:26:40 DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh -o "StrictHostKeyC
2014-05-07 18:26:42 INFO juju.environs.
2014-05-07 18:26:42 INFO juju.environs.
2014-05-07 18:26:42 DEBUG juju.utils.ssh ssh.go:234 using OpenSSH ssh client
2014-05-07 18:26:42 DEBUG juju.utils.ssh ssh_openssh.go:122 running: ssh -o "StrictHostKeyC
2014-05-07 18:26:43 INFO juju.environs.
2014-05-07 18:26:43 ERROR juju.cmd supercommand.go:304 no such request - method Client.