Activity log for bug #1321212

Date Who What changed Old value New value Message
2014-05-20 09:49:17 Matthew Williams bug added bug
2014-05-20 20:27:17 Curtis Hovey tags ha
2014-05-20 20:34:45 Curtis Hovey tags ha ha ui usability
2014-05-20 20:34:49 Curtis Hovey juju-core: status New Triaged
2014-05-20 20:34:52 Curtis Hovey juju-core: milestone next-stable
2014-05-20 20:34:54 Curtis Hovey juju-core: importance Undecided High
2014-10-28 21:03:21 Curtis Hovey juju-core: importance High Medium
2014-10-28 21:03:21 Curtis Hovey juju-core: milestone next-stable
2015-06-09 16:08:04 Katherine Cox-Buday description As you can see from this paste: http://pastebin.ubuntu.com/7492326/ I run bootstrap, then ensure-availability. 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? 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-224-242-90.compute-1.amazonaws.com instance-id: i-76c37325 instance-state: running series: precise hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M state-server-member-status: has-vote "1": agent-state: pending dns-name: ec2-54-83-244-194.compute-1.amazonaws.com instance-id: i-83ca7ad0 instance-state: running series: precise hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M state-server-member-status: adding-vote "2": agent-state: pending dns-name: ec2-107-20-131-219.compute-1.amazonaws.com instance-id: i-28cf7f7b instance-state: running series: precise hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M state-server-member-status: adding-vote services: {} I run bootstrap, then ensure-availability. 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?
2015-06-09 16:22:54 Katherine Cox-Buday summary Odd behaviour when using ensure-availability juju status reporting API server connection error while bringing up new state servers
2016-09-22 00:34:14 Alexis Bruemmer juju-core: status Triaged Won't Fix