[CI-results] Build failed in Jenkins: gluster_anteater_gcs #37
ci at centos.org
ci at centos.org
Thu Jan 3 02:14:45 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/37/display/redirect>
------------------------------------------
[...truncated 582.74 KB...]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 03 January 2019 00:56:43 +0000 (0:00:01.598) 0:19:33.288 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Thursday 03 January 2019 00:56:43 +0000 (0:00:00.304) 0:19:33.593 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Thursday 03 January 2019 00:56:45 +0000 (0:00:01.512) 0:19:35.105 ******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Thursday 03 January 2019 00:56:47 +0000 (0:00:01.514) 0:19:36.620 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Thursday 03 January 2019 00:56:47 +0000 (0:00:00.329) 0:19:36.950 ******
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices] *****************************************
Thursday 03 January 2019 00:57:14 +0000 (0:00:27.116) 0:20:04.066 ******
included: /root/gcs/deploy/tasks/add-devices-to-peer.yml for kube1
included: /root/gcs/deploy/tasks/add-devices-to-peer.yml for kube1
included: /root/gcs/deploy/tasks/add-devices-to-peer.yml for kube1
TASK [GCS | GD2 Cluster | Add devices | Set facts] *****************************
Thursday 03 January 2019 00:57:14 +0000 (0:00:00.313) 0:20:04.380 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices | Add devices for kube1] *****************
Thursday 03 January 2019 00:57:15 +0000 (0:00:00.370) 0:20:04.750 ******
ok: [kube1] => (item=/dev/vdc)
ok: [kube1] => (item=/dev/vdd)
ok: [kube1] => (item=/dev/vde)
TASK [GCS | GD2 Cluster | Add devices | Set facts] *****************************
Thursday 03 January 2019 00:57:20 +0000 (0:00:05.676) 0:20:10.427 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices | Add devices for kube3] *****************
Thursday 03 January 2019 00:57:21 +0000 (0:00:00.408) 0:20:10.835 ******
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (1 retries left).
failed: [kube1] (item=/dev/vdc) => {"attempts": 50, "changed": false, "content": "", "disk": "/dev/vdc", "msg": "Status code was -1 and not [201]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://10.233.1.27:24007/v1/devices/79bbb85c-5196-4f1e-a66e-63b57135e79a"}
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (1 retries left).
failed: [kube1] (item=/dev/vdd) => {"attempts": 50, "changed": false, "content": "", "disk": "/dev/vdd", "msg": "Status code was -1 and not [201]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://10.233.1.27:24007/v1/devices/79bbb85c-5196-4f1e-a66e-63b57135e79a"}
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube3 (1 retries left).
failed: [kube1] (item=/dev/vde) => {"attempts": 50, "changed": false, "content": "", "disk": "/dev/vde", "msg": "Status code was -1 and not [201]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://10.233.1.27:24007/v1/devices/79bbb85c-5196-4f1e-a66e-63b57135e79a"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=389 changed=113 unreachable=0 failed=1
kube2 : ok=293 changed=91 unreachable=0 failed=0
kube3 : ok=255 changed=71 unreachable=0 failed=0
Thursday 03 January 2019 02:14:44 +0000 (1:17:23.764) 1:37:34.600 ******
===============================================================================
GCS | GD2 Cluster | Add devices | Add devices for kube3 -------------- 4643.76s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 96.50s
kubernetes/master : Master | wait for the apiserver to be running ------ 43.89s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 40.26s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.87s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 31.77s
Install packages ------------------------------------------------------- 30.01s
kubernetes/master : Master | wait for kube-controller-manager ---------- 28.86s
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready --------- 27.12s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 26.48s
Wait for host to be available ------------------------------------------ 20.90s
download : file_download | Download item ------------------------------- 14.61s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.02s
gather facts from all instances ---------------------------------------- 12.73s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.44s
etcd : reload etcd ----------------------------------------------------- 11.85s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.38s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 11.16s
docker : Docker | pause while Docker restarts -------------------------- 10.38s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 9.55s
==> 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