[CI-results] Build failed in Jenkins: gluster_anteater_gcs #91
ci at centos.org
ci at centos.org
Sat Mar 2 06:09:49 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/91/display/redirect>
------------------------------------------
[...truncated 465.53 KB...]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 02 March 2019 05:05:00 +0000 (0:00:01.563) 0:20:31.515 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Saturday 02 March 2019 05:05:00 +0000 (0:00:00.341) 0:20:31.856 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 02 March 2019 05:05:02 +0000 (0:00:01.574) 0:20:33.431 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Saturday 02 March 2019 05:05:02 +0000 (0:00:00.334) 0:20:33.765 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Saturday 02 March 2019 05:05:04 +0000 (0:00:01.725) 0:20:35.491 ********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Saturday 02 March 2019 05:05:06 +0000 (0:00:02.058) 0:20:37.550 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Saturday 02 March 2019 05:05:06 +0000 (0:00:00.304) 0:20:37.854 ********
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices] *****************************************
Saturday 02 March 2019 05:05:56 +0000 (0:00:50.095) 0:21:27.950 ********
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] *****************************
Saturday 02 March 2019 05:05:57 +0000 (0:00:00.330) 0:21:28.280 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices | Add devices for kube2] *****************
Saturday 02 March 2019 05:05:57 +0000 (0:00:00.377) 0:21:28.658 ********
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (1 retries left).
failed: [kube1] (item=/dev/vdc) => {"attempts": 50, "changed": false, "content": "", "disk": "/dev/vdc", "msg": "Status code was -1 and not [201]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://10.233.27.233:24007/v1/devices/4a271b2e-ca8e-4758-a00a-af57ba905606"}
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (1 retries left).
failed: [kube1] (item=/dev/vdd) => {"attempts": 50, "changed": false, "content": "", "disk": "/dev/vdd", "msg": "Status code was -1 and not [201]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://10.233.27.233:24007/v1/devices/4a271b2e-ca8e-4758-a00a-af57ba905606"}
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (50 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (49 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (48 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (47 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Add devices | Add devices for kube2 (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.27.233:24007/v1/devices/4a271b2e-ca8e-4758-a00a-af57ba905606"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=426 changed=119 unreachable=0 failed=1
kube2 : ok=320 changed=93 unreachable=0 failed=0
kube3 : ok=283 changed=78 unreachable=0 failed=0
Saturday 02 March 2019 06:09:48 +0000 (1:03:51.141) 1:25:19.800 ********
===============================================================================
GCS | GD2 Cluster | Add devices | Add devices for kube2 -------------- 3831.14s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.79s
download : container_download | download images for kubeadm config images -- 51.59s
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready --------- 50.10s
kubernetes/master : kubeadm | Initialize first master ------------------ 40.76s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 39.57s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.26s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.22s
Install packages ------------------------------------------------------- 30.23s
Wait for host to be available ------------------------------------------ 20.92s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.53s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 19.15s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 17.33s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.32s
gather facts from all instances ---------------------------------------- 13.31s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.61s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.15s
etcd : reload etcd ----------------------------------------------------- 11.86s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.70s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.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