juju add-machine manual on fresh EC2 instance hangs, juju 2.8.11
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Incomplete
|
Undecided
|
Vitaly Antonenko | ||
Bug Description
I am able to consistently create a hang state when adding a new EC2 instance to a fresh controller+model on EC2 with a focal based controller instance. I am using juju 2.8.11.
For reference, the controller was bootstrapped like so:
juju bootstrap --config vpc-id-force=true --config vpc-id=some-vpc --constraints "instance-
I am able to SSH to both the controller and the new instance before attempting to add the instance to my model. I also noticed that the db-service on the controller was disabled:
snap-juju\
jujud-machine-
snap.juju-
After re-enabling the service I was able to finally add the machine without hanging, but I'm not sure if this was the actual cause.
Debug log from add-machine (192.168.99.62 is the instance IP, 192.168.99.27 is the controller):
juju add-machine -m ec2controller:
16:54:47 INFO juju.cmd supercommand.go:54 running juju [2.8.11 0 5e99fae0eff8e18
16:54:47 DEBUG juju.cmd supercommand.go:55 args: []string{
16:54:47 INFO juju.juju api.go:67 connecting to API addresses: [192.168.
16:54:47 DEBUG juju.api apiclient.go:1116 successfully dialed "wss://
16:54:47 INFO juju.api apiclient.go:648 connection established to "wss://
16:54:47 INFO juju.juju api.go:67 connecting to API addresses: [192.168.
16:54:47 DEBUG juju.api apiclient.go:1116 successfully dialed "wss://
16:54:47 INFO juju.api apiclient.go:648 connection established to "wss://
16:54:47 INFO juju.cmd.
16:54:47 INFO juju.juju api.go:67 connecting to API addresses: [192.168.
16:54:47 DEBUG juju.api apiclient.go:1116 successfully dialed "wss://
16:54:47 INFO juju.api apiclient.go:648 connection established to "wss://
16:54:47 INFO juju.juju api.go:304 API endpoints changed from [252.99.96.1:17070 192.168.
16:54:47 INFO cmd authkeys.go:114 Adding contents of "/home/
16:54:47 INFO cmd authkeys.go:114 Adding contents of "/home/
16:54:47 INFO juju.environs.
16:54:47 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
16:54:49 INFO juju.environs.
16:54:49 INFO juju.environs.
16:54:49 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
16:54:50 INFO juju.environs.
16:54:50 DEBUG juju.utils.ssh ssh.go:305 using OpenSSH ssh client
16:54:51 INFO juju.environs.
16:59:17 ERROR juju.api monitor.go:59 health ping timed out after 30s
16:59:17 ERROR juju.api monitor.go:59 health ping timed out after 30s
16:59:17 ERROR juju.api monitor.go:59 health ping timed out after 30s
Timeout, server 192.168.99.62 not responding.
17:00:28 ERROR juju.environs.
| summary: |
- juju add-machine manual on fresh EC2 instance, juju 2.8.11 + juju add-machine manual on fresh EC2 instance hangs, juju 2.8.11 |
| Sheldon Ruiz (sherui01) wrote | #1 |
| Vitaly Antonenko (anvial) wrote | #2 |
| Changed in juju: | |
| status: | New → Incomplete |
| assignee: | nobody → Vitaly Antonenko (anvial) |
I've also noticed that sometimes, if I successfully was able to create a focal controller+model, when adding a charm to the model Juju will hang here as well. No error or anything.