add-machine fails when using IP in ssh: target
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
It appears there's an issue with targeting IP addresses in "add-machine ssh:...". We shouldn't be passing an IP into net.LookupIP.
From Matthew Williams:
---
I tried bootstrapping in aws then adding a machine supplied by digital ocean. I got an invalid domain error. Any idea what I was doing wrong?
juju add-machine -v ssh:root@
2013-09-15 20:06:07 INFO juju.provider.ec2 ec2.go:187 opening environment "amazon"
2013-09-15 20:06:12 INFO juju.state open.go:68 opening state; mongo addresses: ["ec2-54-
mpute-1.
2013-09-15 20:06:15 INFO juju.state open.go:106 connection established
2013-09-15 20:06:18 INFO juju.provider.ec2 ec2.go:187 opening environment "amazon"
2013-09-15 20:06:18 ERROR juju supercommand.go:282 command failed: lookup 162.243.10.110: invalid dom
ain name
error: lookup 162.243.10.110: invalid domain name
Related branches
- Juju Engineering: Pending requested
-
Diff: 320 lines (+116/-49)3 files modifiedenvirons/manual/provisioner.go (+13/-0)
instance/address.go (+20/-6)
instance/address_test.go (+83/-43)
Changed in juju-core: | |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Note: this only happens when using the non-cgo version of "net".