[CI-results] Build failed in Jenkins: gluster_anteater_gcs #96
ci at centos.org
ci at centos.org
Wed Mar 6 03:04:01 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/96/display/redirect>
------------------------------------------
[...truncated 465.36 KB...]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 06 March 2019 01:59:52 +0000 (0:00:01.804) 0:21:02.486 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Wednesday 06 March 2019 01:59:52 +0000 (0:00:00.562) 0:21:03.048 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 06 March 2019 01:59:54 +0000 (0:00:01.782) 0:21:04.831 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Wednesday 06 March 2019 01:59:54 +0000 (0:00:00.513) 0:21:05.344 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Wednesday 06 March 2019 01:59:57 +0000 (0:00:02.450) 0:21:07.795 *******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Wednesday 06 March 2019 01:59:58 +0000 (0:00:01.533) 0:21:09.328 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Wednesday 06 March 2019 01:59:59 +0000 (0:00:00.461) 0:21:09.790 *******
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices] *****************************************
Wednesday 06 March 2019 02:00:38 +0000 (0:00:38.760) 0:21:48.551 *******
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] *****************************
Wednesday 06 March 2019 02:00:38 +0000 (0:00:00.317) 0:21:48.868 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices | Add devices for kube2] *****************
Wednesday 06 March 2019 02:00:38 +0000 (0:00:00.464) 0:21:49.332 *******
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.46.45:24007/v1/devices/0b948a5a-2e44-492c-8a42-8afdd988788e"}
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]: Connection failure: timed out", "redirected": false, "status": -1, "url": "http://10.233.46.45:24007/v1/devices/0b948a5a-2e44-492c-8a42-8afdd988788e"}
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.46.45:24007/v1/devices/0b948a5a-2e44-492c-8a42-8afdd988788e"}
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
Wednesday 06 March 2019 03:04:01 +0000 (1:03:22.648) 1:25:11.981 *******
===============================================================================
GCS | GD2 Cluster | Add devices | Add devices for kube2 -------------- 3802.65s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 83.93s
kubernetes/master : kubeadm | Initialize first master ------------------ 40.12s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 39.44s
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready --------- 38.76s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 34.84s
Install packages ------------------------------------------------------- 34.72s
download : container_download | download images for kubeadm config images -- 33.31s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.71s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 21.45s
Wait for host to be available ------------------------------------------ 20.99s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 19.77s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 17.64s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.93s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.76s
gather facts from all instances ---------------------------------------- 13.06s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.20s
etcd : reload etcd ----------------------------------------------------- 11.89s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.38s
container-engine/docker : Docker | pause while Docker restarts --------- 10.44s
==> 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