Unable to add-machine to a manual cloud using SSH

Bug #1967730 reported by Bartlomiej Gmerek
6
This bug affects 1 person
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.19.27:44450->172.31.16.246:17070: write: connection reset by peer
machine-0: 08:55:12 ERROR juju.worker.dependency "migration-minion" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.19.27:44450->172.31.16.246:17070: write: connection reset by peer
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.19.27:44450->172.31.16.246:17070: write: connection reset by peer
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.19.27:44450->172.31.16.246:17070: write: connection reset by peer
machine-0: 08:55:12 ERROR juju.worker.dependency "fan-configurer" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.worker.dependency "log-sender" manifold worker returned unexpected error: sending log message: websocket: close 1006 (abnormal closure): unexpected EOF: use of closed network connection
machine-0: 08:55:12 ERROR juju.worker.dependency "api-address-updater" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.worker.dependency "logging-config-updater" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.worker.dependency "valid-credential-flag" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.worker.dependency "machine-action-runner" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.worker.dependency "migration-inactive-flag" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.worker.dependency "deployer" manifold worker returned unexpected error: watcher has been stopped (stopped)
machine-0: 08:55:12 INFO juju.cmd.jujud.runner runner is dying
machine-0: 08:55:12 ERROR juju.api.watcher error trying to stop watcher: write tcp 172.31.19.27:44450->172.31.16.246:17070: write: connection reset by peer
machine-0: 08:55:12 ERROR juju.worker.dependency "api-caller" manifold worker returned unexpected error: api connection broken unexpectedly
machine-0: 08:55:12 INFO juju.cmd.jujud.runner stopped "stateconverter", err: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.cmd.jujud.runner fatal "stateconverter": watcher has been stopped (stopped)
machine-0: 08:55:12 INFO juju.cmd.jujud.runner stopped "0-container-watcher", err: watcher has been stopped (stopped)
machine-0: 08:55:12 ERROR juju.cmd.jujud.runner fatal "0-container-watcher": watcher has been stopped (stopped)
```

Juju version: 2.9.27

Any idea what may be causing this issue?

BR,
Bartek

Revision history for this message
Ian Booth (wallyworld) wrote :

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.

Revision history for this message
Harry Pidcock (hpidcock) wrote :

If this is still an issue and isn't solved by verifying AWS security groups are correct, please respond with more information and change the status back to new.

Changed in juju:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
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.