[CI-results] Build failed in Jenkins: gluster_anteater_gcs #58
ci at centos.org
ci at centos.org
Thu Jan 24 00:56:18 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/58/display/redirect>
------------------------------------------
[...truncated 458.12 KB...]
changed: [kube1] => (item=gcs-csi.yml)
changed: [kube1] => (item=gcs-storage-snapshot.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] ******************************
Thursday 24 January 2019 00:44:55 +0000 (0:00:10.880) 0:10:08.581 ******
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] ***
Thursday 24 January 2019 00:44:55 +0000 (0:00:00.092) 0:10:08.673 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Thursday 24 January 2019 00:44:55 +0000 (0:00:00.202) 0:10:08.876 ******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Thursday 24 January 2019 00:44:56 +0000 (0:00:00.789) 0:10:09.665 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Thursday 24 January 2019 00:44:56 +0000 (0:00:00.222) 0:10:09.888 ******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Thursday 24 January 2019 00:44:57 +0000 (0:00:00.800) 0:10:10.688 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Thursday 24 January 2019 00:44:57 +0000 (0:00:00.205) 0:10:10.893 ******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Thursday 24 January 2019 00:44:58 +0000 (0:00:00.782) 0:10:11.676 ******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Thursday 24 January 2019 00:44:58 +0000 (0:00:00.708) 0:10:12.384 ******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Thursday 24 January 2019 00:44:59 +0000 (0:00:00.770) 0:10:13.155 ******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (49 retries left).
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (48 retries left).
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (47 retries left).
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (46 retries left).
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (45 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Thursday 24 January 2019 00:46:02 +0000 (0:01:02.670) 0:11:15.825 ******
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Thursday 24 January 2019 00:46:03 +0000 (0:00:00.710) 0:11:16.536 ******
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Thursday 24 January 2019 00:46:03 +0000 (0:00:00.536) 0:11:17.072 ******
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Thursday 24 January 2019 00:46:04 +0000 (0:00:00.483) 0:11:17.555 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Thursday 24 January 2019 00:46:04 +0000 (0:00:00.681) 0:11:18.237 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Thursday 24 January 2019 00:46:05 +0000 (0:00:00.878) 0:11:19.116 ******
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Thursday 24 January 2019 00:46:11 +0000 (0:00:05.858) 0:11:24.974 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Thursday 24 January 2019 00:46:11 +0000 (0:00:00.146) 0:11:25.120 ******
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] *********************************
Thursday 24 January 2019 00:47:17 +0000 (0:01:06.275) 0:12:31.395 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Thursday 24 January 2019 00:47:18 +0000 (0:00:00.746) 0:12:32.142 ******
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] ******************************
Thursday 24 January 2019 00:47:18 +0000 (0:00:00.109) 0:12:32.252 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Thursday 24 January 2019 00:47:18 +0000 (0:00:00.141) 0:12:32.394 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 24 January 2019 00:47:19 +0000 (0:00:00.655) 0:12:33.049 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Thursday 24 January 2019 00:47:19 +0000 (0:00:00.147) 0:12:33.196 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 24 January 2019 00:47:20 +0000 (0:00:00.757) 0:12:33.954 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Thursday 24 January 2019 00:47:20 +0000 (0:00:00.184) 0:12:34.138 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Thursday 24 January 2019 00:47:21 +0000 (0:00:00.760) 0:12:34.899 ******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Thursday 24 January 2019 00:47:22 +0000 (0:00:00.527) 0:12:35.426 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Thursday 24 January 2019 00:47:22 +0000 (0:00:00.214) 0:12:35.641 ******
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.3.172:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=415 changed=115 unreachable=0 failed=1
kube2 : ok=319 changed=91 unreachable=0 failed=0
kube3 : ok=282 changed=77 unreachable=0 failed=0
Thursday 24 January 2019 00:56:17 +0000 (0:08:55.646) 0:21:31.288 ******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 535.65s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 66.28s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 62.67s
download : container_download | download images for kubeadm config images -- 31.95s
kubernetes/master : kubeadm | Initialize first master ------------------ 26.05s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 25.08s
Install packages ------------------------------------------------------- 24.79s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 18.03s
Wait for host to be available ------------------------------------------ 16.44s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.01s
etcd : Gen_certs | Write etcd master certs ----------------------------- 13.54s
Extend root VG --------------------------------------------------------- 13.39s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 11.34s
etcd : reload etcd ----------------------------------------------------- 11.06s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 10.88s
container-engine/docker : Docker | pause while Docker restarts --------- 10.25s
gather facts from all instances ----------------------------------------- 8.49s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 8.03s
download : file_download | Download item -------------------------------- 7.51s
etcd : wait for etcd up ------------------------------------------------- 7.46s
==> 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