Juju-ci3 cannot upgrade to 1.21.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
High
|
Unassigned |
Bug Description
juju-ci3 is in upgrade hell to 1.21.1 state server upgraded in a few minutes, after an hour it fell over. I restarted the agents and can see it, but all the other machines are down. They are trying to contact 10.0.3.1...which is not where the state server is
35 of 36 agents are wrong after buggered upgrade
2015-02-02 21:21:32 INFO juju.worker runner.go:260 start "api"
2015-02-02 21:21:32 INFO juju.state.api apiclient.go:242 dialing "wss://
2015-02-02 21:21:32 INFO juju.state.api apiclient.go:250 error dialing "wss://
2015-02-02 21:21:32 ERROR juju.worker runner.go:218 exited "api": unable to connect to "wss://
2015-02-02 21:21:32 INFO juju.worker runner.go:252 restarting "api" in 3s
The address should be 172.31.9.3 or ip-172-
Setting the apiaddress to ip-172-
an upgrade...
2015-02-02 21:51:04 INFO juju.worker.
2015-02-02 21:51:04 INFO juju.worker.
2015-02-02 21:51:04 INFO juju.utils http.go:66 hostname SSL verification disabled
2015-02-02 21:51:04 ERROR juju.worker.
Which is again the wrong address. Reseting the apiaddress to the private ip
or the private name fails because the value is rewritten to an impossible
value.
Attached is a log from machine-8 (juju-reports, the app behind reports.vapour.ws) We can see the api server was connacted after I changed the api address, but the value is immediately changed back to 10.0.3.1.
I tried changing state-server to 31-9-3. ec2.internal
apiaddress: ip-172-
and restarted, but it like all the other machines are ignoring the value, it is alaways rewritten to 10.0.3.1