Unable to add-machine to a manual cloud using SSH
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello Team,
I'm trying to set up a manual cloud using AWS instances, but I'm having problems with adding a machine over ssh. I have Juju on my laptop and bootstrapped controller in AWS. After adding machine (`juju add-machine ssh:...`) it's visible as started for a couple of seconds and then it goes down. After that it cycles from down to started infinitely.
In `juju debug-log` I get a lot of:
```
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 INFO juju.cmd.
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.
machine-0: 08:55:12 ERROR juju.worker.
machine-0: 08:55:12 INFO juju.cmd.
machine-0: 08:55:12 ERROR juju.cmd.
machine-0: 08:55:12 INFO juju.cmd.
machine-0: 08:55:12 ERROR juju.cmd.
```
Juju version: 2.9.27
Any idea what may be causing this issue?
BR,
Bartek
Juju agents running on machines need to be able to establish a connection to the controller agent. When juju manages the machines on AWS, it creates the necessary security group rules to allow this to happen.
As a guess, maybe the manual machine being added cannot establish a connection to the previously boostrapped controller. You will want to check that for the controller machine, inbound traffic via port 17070 is allowed. You may also need to open port 22 for ssh access from the controller to the manually added machine.