juju status reporting API server connection error while bringing up new state servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
As you can see from this paste:
$ ./juju bootstrap
$ ./juju ensure-availability
$ ./juju status
WARNING discarding API open error: read tcp 127.0.0.1:37017: i/o timeout
ERROR Unable to connect to environment "amazon".
Please check your credentials or use 'juju bootstrap' to create a new environment.
Error details:
read tcp 127.0.0.1:37017: i/o timeout
$ ./juju status
WARNING discarding API open error: read tcp 127.0.0.1:37017: i/o timeout
ERROR Unable to connect to environment "amazon".
Please check your credentials or use 'juju bootstrap' to create a new environment.
Error details:
read tcp 127.0.0.1:37017: i/o timeout
$ ./juju status
environment: amazon
machines:
"0":
agent-state: started
agent-version: 1.19.3.1
dns-name: ec2-54-
instance-id: i-76c37325
instance-state: running
series: precise
hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
state-
"1":
agent-state: pending
dns-name: ec2-54-
instance-id: i-83ca7ad0
instance-state: running
series: precise
hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
state-
"2":
agent-state: pending
dns-name: ec2-107-
instance-id: i-28cf7f7b
instance-state: running
series: precise
hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
state-
services: {}
I run bootstrap, then ensure-
After this step we "appear" to fail to connect to a local state server (despite being configured to use aws)
After sometime the extra state servers come up and we're back in our environment
Is this expected?
tags: | added: ha |
tags: | added: ui usability |
Changed in juju-core: | |
status: | New → Triaged |
milestone: | none → next-stable |
importance: | Undecided → High |
Changed in juju-core: | |
importance: | High → Medium |
milestone: | next-stable → none |
description: | updated |
summary: |
- Odd behaviour when using ensure-availability + juju status reporting API server connection error while bringing up new + state servers |
the error here is actually from the api server which can't connect to its local mongo, but its reported back to the client