[CI-results] Build failed in Jenkins: gluster_anteater_gcs #133
ci at centos.org
ci at centos.org
Wed Apr 10 00:55:33 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/133/display/redirect>
------------------------------------------
[...truncated 459.41 KB...]
changed: [kube1] => (item=gcs-etcd-operator.yml)
changed: [kube1] => (item=gcs-etcd-cluster.yml)
changed: [kube1] => (item=gcs-gd2-services.yml)
changed: [kube1] => (item=gcs-fs-csi.yml)
changed: [kube1] => (item=gcs-storage-snapshot.yml)
changed: [kube1] => (item=gcs-virtblock-csi.yml)
changed: [kube1] => (item=gcs-storage-virtblock.yml)
changed: [kube1] => (item=gcs-prometheus-operator.yml)
changed: [kube1] => (item=gcs-prometheus-bundle.yml)
changed: [kube1] => (item=gcs-prometheus-alertmanager-cluster.yml)
changed: [kube1] => (item=gcs-prometheus-operator-metrics.yml)
changed: [kube1] => (item=gcs-prometheus-kube-state-metrics.yml)
changed: [kube1] => (item=gcs-prometheus-node-exporter.yml)
changed: [kube1] => (item=gcs-prometheus-kube-metrics.yml)
changed: [kube1] => (item=gcs-prometheus-etcd.yml)
changed: [kube1] => (item=gcs-grafana.yml)
changed: [kube1] => (item=gcs-operator-crd.yml)
changed: [kube1] => (item=gcs-operator.yml)
changed: [kube1] => (item=gcs-mixins.yml)
TASK [GCS Pre | Manifests | Create GD2 manifests] ******************************
Wednesday 10 April 2019 01:45:00 +0100 (0:00:11.887) 0:10:20.233 *******
included: /root/gcs/deploy/tasks/create-gd2-manifests.yml for kube1
included: /root/gcs/deploy/tasks/create-gd2-manifests.yml for kube1
included: /root/gcs/deploy/tasks/create-gd2-manifests.yml for kube1
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Set fact kube_hostname] ***
Wednesday 10 April 2019 01:45:00 +0100 (0:00:00.089) 0:10:20.322 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Wednesday 10 April 2019 01:45:01 +0100 (0:00:00.155) 0:10:20.478 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Wednesday 10 April 2019 01:45:01 +0100 (0:00:00.722) 0:10:21.200 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Wednesday 10 April 2019 01:45:01 +0100 (0:00:00.132) 0:10:21.332 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Wednesday 10 April 2019 01:45:02 +0100 (0:00:00.741) 0:10:22.073 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Wednesday 10 April 2019 01:45:02 +0100 (0:00:00.151) 0:10:22.225 *******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Wednesday 10 April 2019 01:45:03 +0100 (0:00:00.750) 0:10:22.975 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Wednesday 10 April 2019 01:45:04 +0100 (0:00:00.648) 0:10:23.623 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Wednesday 10 April 2019 01:45:04 +0100 (0:00:00.679) 0:10:24.303 *******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Wednesday 10 April 2019 01:45:15 +0100 (0:00:10.872) 0:10:35.175 *******
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Wednesday 10 April 2019 01:45:16 +0100 (0:00:00.641) 0:10:35.817 *******
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Wednesday 10 April 2019 01:45:16 +0100 (0:00:00.462) 0:10:36.279 *******
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Wednesday 10 April 2019 01:45:17 +0100 (0:00:00.477) 0:10:36.757 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Wednesday 10 April 2019 01:45:17 +0100 (0:00:00.698) 0:10:37.456 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Wednesday 10 April 2019 01:45:18 +0100 (0:00:00.862) 0:10:38.318 *******
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Wednesday 10 April 2019 01:45:24 +0100 (0:00:06.018) 0:10:44.337 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Wednesday 10 April 2019 01:45:25 +0100 (0:00:00.137) 0:10:44.474 *******
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (50 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (49 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (48 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (47 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (46 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (45 retries left).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Wednesday 10 April 2019 01:46:30 +0100 (0:01:05.164) 0:11:49.639 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Wednesday 10 April 2019 01:46:30 +0100 (0:00:00.827) 0:11:50.466 *******
included: /root/gcs/deploy/tasks/deploy-gd2.yml for kube1
included: /root/gcs/deploy/tasks/deploy-gd2.yml for kube1
included: /root/gcs/deploy/tasks/deploy-gd2.yml for kube1
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 10 April 2019 01:46:31 +0100 (0:00:00.096) 0:11:50.562 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Wednesday 10 April 2019 01:46:31 +0100 (0:00:00.136) 0:11:50.699 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 10 April 2019 01:46:31 +0100 (0:00:00.719) 0:11:51.419 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Wednesday 10 April 2019 01:46:32 +0100 (0:00:00.142) 0:11:51.561 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 10 April 2019 01:46:32 +0100 (0:00:00.846) 0:11:52.408 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Wednesday 10 April 2019 01:46:33 +0100 (0:00:00.224) 0:11:52.632 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Wednesday 10 April 2019 01:46:33 +0100 (0:00:00.794) 0:11:53.427 *******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Wednesday 10 April 2019 01:46:34 +0100 (0:00:00.548) 0:11:53.976 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Wednesday 10 April 2019 01:46:34 +0100 (0:00:00.277) 0:11:54.254 *******
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (1 retries left).
fatal: [kube1]: FAILED! => {"attempts": 50, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://10.233.48.207:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=421 changed=119 unreachable=0 failed=1
kube2 : ok=320 changed=93 unreachable=0 failed=0
kube3 : ok=283 changed=78 unreachable=0 failed=0
Wednesday 10 April 2019 01:55:32 +0100 (0:08:58.208) 0:20:52.463 *******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 538.21s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 65.16s
download : container_download | download images for kubeadm config images -- 35.43s
kubernetes/master : kubeadm | Initialize first master ------------------ 26.21s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 25.25s
Install packages ------------------------------------------------------- 23.46s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.37s
Wait for host to be available ------------------------------------------ 16.36s
Extend root VG --------------------------------------------------------- 14.07s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 12.69s
etcd : Gen_certs | Write etcd master certs ----------------------------- 12.61s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 11.89s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 11.63s
etcd : reload etcd ----------------------------------------------------- 10.97s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.87s
kubernetes/node : install | Copy hyperkube binary from download dir ---- 10.54s
container-engine/docker : Docker | pause while Docker restarts --------- 10.19s
download : file_download | Download item -------------------------------- 9.01s
gather facts from all instances ----------------------------------------- 8.59s
etcd : wait for etcd up ------------------------------------------------- 7.47s
==> kube3: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
An error occurred while executing the action on the 'kube3'
machine. Please handle this error then try again:
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build started : False
Logical operation result is FALSE
Skipping script : # cico-node-done-from-ansible.sh
# A script that releases nodes from a SSID file written by
SSID_FILE=${SSID_FILE:-$WORKSPACE/cico-ssid}
for ssid in $(cat ${SSID_FILE})
do
cico -q node done $ssid
done
END OF POST BUILD TASK : 0
More information about the ci-results
mailing list