environs/ec2: if the bootstrap node is stopped and started, all the agents in the environment cannot reconnect (new IP address)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Today I was using my ec2 test environment when AWS shutdown my bootstrap node. After restarting it in the console, none of the agents in the environment could reconnect.
2013-10-08 01:31:38 ERROR juju apiclient.go:116 state/api: websocket.Dial wss://ec2-
2013-10-08 01:31:38 ERROR juju runner.go:211 worker: exited "api": websocket.Dial wss://ec2-
2013-10-08 01:31:38 INFO juju runner.go:245 worker: restarting "api" in 3s
2013-10-08 01:31:41 INFO juju runner.go:253 worker: start "api"
2013-10-08 01:31:41 INFO juju apiclient.go:111 state/api: dialing "wss://
2013-10-08 01:32:44 ERROR juju apiclient.go:116 state/api: websocket.Dial wss://ec2-
2013-10-08 01:32:44 ERROR juju runner.go:211 worker: exited "api": websocket.Dial wss://ec2-
2013-10-08 01:32:44 INFO juju runner.go:245 worker: restarting "api" in 3s
2013-10-08 01:32:47 INFO juju runner.go:253 worker: start "api"
2013-10-08 01:32:47 INFO juju apiclient.go:111 state/api: dialing "wss://
| tags: | added: state-server |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: ec2 |
| summary: |
- environs/ec2: if the bootstrap node is restarted, all the agents in the - environment cannot reconnect + environs/ec2: if the bootstrap node is stopped and started, all the + agents in the environment cannot reconnect (new IP address) |
| tags: |
added: ec2-provider removed: ec2 |
| Changed in juju-core: | |
| importance: | High → Medium |
| Dimiter Naydenov (dimitern) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Released |
This should be fixed now, as the instance addresses are updated regularly. Dave, can you confirm if this still happens?