[CI-results] Build failed in Jenkins: gluster_anteater_gcs #53
ci at centos.org
ci at centos.org
Sat Jan 19 02:00:51 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/53/display/redirect?page=changes>
Changes:
[nigelb] Add a debugging command
[nigelb] Move ssh-keygen to shell
[nigelb] Remove need to generate ssh-keys
[nigelb] Update pip and setup tools before installing docx
------------------------------------------
[...truncated 464.52 KB...]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 19 January 2019 00:57:33 +0000 (0:00:01.739) 0:20:17.380 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Saturday 19 January 2019 00:57:34 +0000 (0:00:00.482) 0:20:17.862 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 19 January 2019 00:57:35 +0000 (0:00:01.716) 0:20:19.578 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Saturday 19 January 2019 00:57:36 +0000 (0:00:00.324) 0:20:19.903 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Saturday 19 January 2019 00:57:37 +0000 (0:00:01.596) 0:20:21.499 ******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Saturday 19 January 2019 00:57:39 +0000 (0:00:01.345) 0:20:22.845 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Saturday 19 January 2019 00:57:39 +0000 (0:00:00.334) 0:20:23.180 ******
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 19 January 2019 00:58:29 +0000 (0:00:49.834) 0:21:13.014 ******
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 19 January 2019 00:58:29 +0000 (0:00:00.331) 0:21:13.346 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Add devices | Add devices for kube2] *****************
Saturday 19 January 2019 00:58:30 +0000 (0:00:00.458) 0:21:13.804 ******
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.33.230:24007/v1/devices/5c4c37ad-eaa8-4511-b297-f4efeb958905"}
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.33.230:24007/v1/devices/5c4c37ad-eaa8-4511-b297-f4efeb958905"}
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.33.230:24007/v1/devices/5c4c37ad-eaa8-4511-b297-f4efeb958905"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=421 changed=115 unreachable=0 failed=1
kube2 : ok=319 changed=91 unreachable=0 failed=0
kube3 : ok=281 changed=77 unreachable=0 failed=0
Saturday 19 January 2019 02:00:51 +0000 (1:02:21.408) 1:23:35.213 ******
===============================================================================
GCS | GD2 Cluster | Add devices | Add devices for kube2 -------------- 3741.41s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------ 107.53s
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready --------- 49.83s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.85s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 37.61s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.67s
download : container_download | download images for kubeadm config images -- 32.95s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 31.97s
Install packages ------------------------------------------------------- 30.83s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 21.02s
Wait for host to be available ------------------------------------------ 20.80s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 19.17s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.69s
etcd : wait for etcd up ------------------------------------------------ 16.28s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.16s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.92s
gather facts from all instances ---------------------------------------- 12.61s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.28s
etcd : reload etcd ----------------------------------------------------- 11.71s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.36s
==> 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