[CI-results] Build failed in Jenkins: gluster_anteater_gcs #46

ci at centos.org ci at centos.org
Sat Jan 12 01:16:08 UTC 2019


See <https://ci.centos.org/job/gluster_anteater_gcs/46/display/redirect>

------------------------------------------
[...truncated 459.32 KB...]
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] ***
Saturday 12 January 2019  00:54:25 +0000 (0:00:00.296)       0:17:21.972 ****** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Saturday 12 January 2019  00:54:25 +0000 (0:00:00.414)       0:17:22.387 ****** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Saturday 12 January 2019  00:54:27 +0000 (0:00:02.061)       0:17:24.448 ****** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Saturday 12 January 2019  00:54:28 +0000 (0:00:00.444)       0:17:24.893 ****** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Saturday 12 January 2019  00:54:30 +0000 (0:00:02.029)       0:17:26.923 ****** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Saturday 12 January 2019  00:54:30 +0000 (0:00:00.434)       0:17:27.357 ****** 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Saturday 12 January 2019  00:54:33 +0000 (0:00:02.158)       0:17:29.515 ****** 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Saturday 12 January 2019  00:54:34 +0000 (0:00:01.515)       0:17:31.031 ****** 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Saturday 12 January 2019  00:54:36 +0000 (0:00:01.663)       0:17:32.694 ****** 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Saturday 12 January 2019  00:54:48 +0000 (0:00:12.206)       0:17:44.901 ****** 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Saturday 12 January 2019  00:54:50 +0000 (0:00:01.769)       0:17:46.671 ****** 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Saturday 12 January 2019  00:54:51 +0000 (0:00:01.380)       0:17:48.051 ****** 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Saturday 12 January 2019  00:54:52 +0000 (0:00:01.359)       0:17:49.410 ****** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Saturday 12 January 2019  00:54:54 +0000 (0:00:01.817)       0:17:51.228 ****** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Saturday 12 January 2019  00:54:56 +0000 (0:00:01.852)       0:17:53.080 ****** 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Saturday 12 January 2019  00:54:57 +0000 (0:00:01.139)       0:17:54.220 ****** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Saturday 12 January 2019  00:54:58 +0000 (0:00:00.522)       0:17:54.742 ****** 
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).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (44 retries left).
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Saturday 12 January 2019  00:56:22 +0000 (0:01:24.211)       0:19:18.954 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Saturday 12 January 2019  00:56:24 +0000 (0:00:01.809)       0:19:20.764 ****** 
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] ******************************
Saturday 12 January 2019  00:56:24 +0000 (0:00:00.192)       0:19:20.956 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Saturday 12 January 2019  00:56:24 +0000 (0:00:00.475)       0:19:21.432 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 12 January 2019  00:56:26 +0000 (0:00:01.573)       0:19:23.005 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Saturday 12 January 2019  00:56:27 +0000 (0:00:00.485)       0:19:23.491 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 12 January 2019  00:56:28 +0000 (0:00:01.778)       0:19:25.270 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Saturday 12 January 2019  00:56:29 +0000 (0:00:00.447)       0:19:25.717 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Saturday 12 January 2019  00:56:31 +0000 (0:00:01.830)       0:19:27.548 ****** 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Saturday 12 January 2019  00:56:32 +0000 (0:00:01.594)       0:19:29.143 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Saturday 12 January 2019  00:56:33 +0000 (0:00:00.578)       0:19:29.722 ****** 
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] *****************************************
Saturday 12 January 2019  00:57:10 +0000 (0:00:37.748)       0:20:07.470 ****** 
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 12 January 2019  00:57:11 +0000 (0:00:00.287)       0:20:07.758 ****** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Add devices | Add devices for kube3] *****************
Saturday 12 January 2019  00:57:11 +0000 (0:00:00.540)       0:20:08.299 ****** 
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).
ok: [kube1] => (item=/dev/vdc)
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).
ok: [kube1] => (item=/dev/vdd)
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.35.137:24007/v1/devices/3a016c39-e94a-4ad2-b8fc-44a4b0f2d503"}
	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 12 January 2019  01:16:08 +0000 (0:18:56.657)       0:39:04.956 ****** 
=============================================================================== 
GCS | GD2 Cluster | Add devices | Add devices for kube3 -------------- 1136.66s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.21s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.65s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 37.76s
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready --------- 37.75s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.99s
download : container_download | download images for kubeadm config images -- 32.96s
Install packages ------------------------------------------------------- 30.53s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 29.51s
Wait for host to be available ------------------------------------------ 21.04s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.96s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.68s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 17.09s
gather facts from all instances ---------------------------------------- 13.34s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.18s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.74s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.21s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.40s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.23s
container-engine/docker : Docker | pause while Docker restarts --------- 10.41s
==> 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