health ping timed out on controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned |
Bug Description
On our solutions qa run, creating a controller on an existing openstack gives an error below.
ERROR:root:ERROR health ping timed out after 30s
ERROR connection is shut down
It's not clear what juju is trying to ping and juju status shows 3 nodes are active.
juju status:
model:
name: controller
type: iaas
controller: foundation-
cloud: openstack_cloud
region: RegionOne
version: 2.6.8
model-status:
current: available
since: 21 Sep 2019 16:53:33Z
sla: unsupported
machines:
"0":
juju-status:
current: started
since: 21 Sep 2019 16:53:45Z
version: 2.6.8
dns-name: 10.244.32.227
ip-addresses:
- 10.244.32.227
- 172.16.0.226
- 252.226.0.1
instance-id: 8dcbfa60-
machine-status:
current: running
message: ACTIVE
since: 21 Sep 2019 16:53:53Z
modificatio
current: idle
since: 21 Sep 2019 16:53:35Z
series: bionic
network-
ens3:
- 172.16.0.226
gateway: 172.16.0.1
is-up: true
fan-252:
- 252.226.0.1
is-up: true
constraints: mem=3584M
hardware: arch=amd64 cores=2 mem=4096M root-disk=40960M availability-
controller-
"1":
juju-status:
current: started
since: 21 Sep 2019 16:55:02Z
version: 2.6.8
dns-name: 10.244.32.53
ip-addresses:
- 10.244.32.53
- 172.16.0.13
- 252.13.0.1
instance-id: 719ed928-
machine-status:
current: running
message: ACTIVE
since: 21 Sep 2019 16:54:29Z
modificatio
current: idle
since: 21 Sep 2019 16:53:48Z
series: bionic
network-
ens3:
- 172.16.0.13
gateway: 172.16.0.1
is-up: true
fan-252:
- 252.13.0.1
is-up: true
hardware: arch=amd64 cores=1 mem=2048M root-disk=20480M availability-
"2":
juju-status:
current: started
since: 21 Sep 2019 16:55:01Z
version: 2.6.8
dns-name: 10.244.32.48
ip-addresses:
- 10.244.32.48
- 172.16.0.229
- 252.229.0.1
instance-id: 13ac4f9d-
machine-status:
current: running
message: ACTIVE
since: 21 Sep 2019 16:54:36Z
modificatio
current: idle
since: 21 Sep 2019 16:53:49Z
series: bionic
network-
ens3:
- 172.16.0.229
gateway: 172.16.0.1
is-up: true
fan-252:
- 252.229.0.1
is-up: true
hardware: arch=amd64 cores=1 mem=2048M root-disk=20480M availability-
applications:
juju-
charm: cs:~juju-
series: bionic
os: ubuntu
charm-origin: jujucharms
charm-name: juju-introspect
charm-rev: 2
exposed: false
application
current: active
message: serving metrics
since: 21 Sep 2019 16:55:26Z
relations:
container:
- ubuntu
subordinate-to:
- ubuntu
endpoint-
container: ""
ubuntu:
charm: cs:ubuntu-12
series: bionic
os: ubuntu
charm-origin: jujucharms
charm-name: ubuntu
charm-rev: 12
exposed: false
application
current: active
message: ready
since: 21 Sep 2019 16:54:44Z
relations:
juju-info:
- juju-introspect
units:
ubuntu/0:
current: active
message: ready
since: 21 Sep 2019 16:54:44Z
current: idle
since: 21 Sep 2019 16:54:45Z
version: 2.6.8
leader: true
machine: "0"
leader: true
- 19090/tcp
ubuntu/1:
current: active
message: ready
since: 21 Sep 2019 16:55:51Z
current: idle
since: 21 Sep 2019 16:55:52Z
version: 2.6.8
machine: "1"
- 19090/tcp
ubuntu/2:
current: active
message: ready
since: 21 Sep 2019 16:55:52Z
current: idle
since: 21 Sep 2019 16:55:54Z
version: 2.6.8
machine: "2"
- 19090/tcp
version: "18.04"
storage: {}
controller:
timestamp: 17:14:47Z
https:/
Changed in juju: | |
importance: | Undecided → High |
status: | New → Incomplete |
Changed in juju: | |
milestone: | 2.8.7 → 3.0.0 |
milestone: | 3.0.0 → 2.8.7 |
Changed in juju: | |
milestone: | 2.8.7 → 2.9.1 |
Changed in juju: | |
milestone: | 2.9.1 → 2.9.2 |
Changed in juju: | |
milestone: | 2.9.2 → 2.9.3 |
Sorry, maybe I'm missing it. What command was in flight during the ping timeout? You mention creating a controller on an openstack base but then status has deployed applications so it's not a fresh bootstrap?