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

ci at centos.org ci at centos.org
Sun Feb 3 00:55:34 UTC 2019


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

------------------------------------------
[...truncated 458.40 KB...]
changed: [kube1] => (item=gcs-etcd-operator.yml)
changed: [kube1] => (item=gcs-etcd-cluster.yml)
changed: [kube1] => (item=gcs-gd2-services.yml)
changed: [kube1] => (item=gcs-csi.yml)
changed: [kube1] => (item=gcs-storage-snapshot.yml)
changed: [kube1] => (item=gcs-prometheus-operator.yml)
changed: [kube1] => (item=gcs-prometheus-bundle.yml)
changed: [kube1] => (item=gcs-prometheus-alertmanager-cluster.yml)
changed: [kube1] => (item=gcs-prometheus-operator-metrics.yml)
changed: [kube1] => (item=gcs-prometheus-kube-state-metrics.yml)
changed: [kube1] => (item=gcs-prometheus-node-exporter.yml)
changed: [kube1] => (item=gcs-prometheus-kube-metrics.yml)
changed: [kube1] => (item=gcs-prometheus-etcd.yml)
changed: [kube1] => (item=gcs-grafana.yml)
changed: [kube1] => (item=gcs-operator-crd.yml)
changed: [kube1] => (item=gcs-operator.yml)
changed: [kube1] => (item=gcs-mixins.yml)

TASK [GCS Pre | Manifests | Create GD2 manifests] ******************************
Sunday 03 February 2019  00:44:45 +0000 (0:00:11.864)       0:10:06.301 ******* 
included: /root/gcs/deploy/tasks/create-gd2-manifests.yml for kube1
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] ***
Sunday 03 February 2019  00:44:46 +0000 (0:00:00.089)       0:10:06.391 ******* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Sunday 03 February 2019  00:44:46 +0000 (0:00:00.151)       0:10:06.543 ******* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Sunday 03 February 2019  00:44:46 +0000 (0:00:00.720)       0:10:07.263 ******* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Sunday 03 February 2019  00:44:47 +0000 (0:00:00.152)       0:10:07.415 ******* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Sunday 03 February 2019  00:44:47 +0000 (0:00:00.741)       0:10:08.157 ******* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Sunday 03 February 2019  00:44:47 +0000 (0:00:00.149)       0:10:08.307 ******* 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Sunday 03 February 2019  00:44:48 +0000 (0:00:00.735)       0:10:09.043 ******* 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Sunday 03 February 2019  00:44:49 +0000 (0:00:00.725)       0:10:09.768 ******* 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Sunday 03 February 2019  00:44:50 +0000 (0:00:00.653)       0:10:10.422 ******* 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Sunday 03 February 2019  00:45:00 +0000 (0:00:10.831)       0:10:21.253 ******* 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Sunday 03 February 2019  00:45:01 +0000 (0:00:00.676)       0:10:21.930 ******* 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Sunday 03 February 2019  00:45:02 +0000 (0:00:00.470)       0:10:22.401 ******* 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Sunday 03 February 2019  00:45:02 +0000 (0:00:00.474)       0:10:22.875 ******* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Sunday 03 February 2019  00:45:03 +0000 (0:00:00.669)       0:10:23.545 ******* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Sunday 03 February 2019  00:45:04 +0000 (0:00:00.870)       0:10:24.415 ******* 
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Sunday 03 February 2019  00:45:10 +0000 (0:00:05.978)       0:10:30.394 ******* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Sunday 03 February 2019  00:45:10 +0000 (0:00:00.145)       0:10:30.540 ******* 
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).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (43 retries left).
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Sunday 03 February 2019  00:46:36 +0000 (0:01:26.294)       0:11:56.834 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Sunday 03 February 2019  00:46:37 +0000 (0:00:00.744)       0:11:57.579 ******* 
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] ******************************
Sunday 03 February 2019  00:46:37 +0000 (0:00:00.112)       0:11:57.691 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Sunday 03 February 2019  00:46:37 +0000 (0:00:00.140)       0:11:57.831 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Sunday 03 February 2019  00:46:38 +0000 (0:00:00.666)       0:11:58.498 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Sunday 03 February 2019  00:46:38 +0000 (0:00:00.149)       0:11:58.647 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Sunday 03 February 2019  00:46:39 +0000 (0:00:00.783)       0:11:59.431 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Sunday 03 February 2019  00:46:39 +0000 (0:00:00.163)       0:11:59.594 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Sunday 03 February 2019  00:46:39 +0000 (0:00:00.717)       0:12:00.311 ******* 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Sunday 03 February 2019  00:46:40 +0000 (0:00:00.507)       0:12:00.819 ******* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Sunday 03 February 2019  00:46:40 +0000 (0:00:00.169)       0:12:00.989 ******* 
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).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (46 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (45 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (44 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (43 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (42 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (41 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (40 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (39 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (38 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (37 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (36 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (35 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (34 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (33 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (32 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (31 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (30 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (29 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (28 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (27 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (26 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (25 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (24 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (23 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (22 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (21 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (20 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (19 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (18 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (17 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (16 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (15 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (14 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (13 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (12 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (11 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (10 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (9 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (8 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (7 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (6 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (5 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (4 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (3 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (2 retries left).
FAILED - RETRYING: GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready (1 retries left).
fatal: [kube1]: FAILED! => {"attempts": 50, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://10.233.15.186:24007/v1/peers"}
	to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry

PLAY RECAP *********************************************************************
kube1                      : ok=416  changed=115  unreachable=0    failed=1   
kube2                      : ok=319  changed=91   unreachable=0    failed=0   
kube3                      : ok=281  changed=77   unreachable=0    failed=0   

Sunday 03 February 2019  00:55:34 +0000 (0:08:53.670)       0:20:54.660 ******* 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 533.67s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 86.29s
download : container_download | download images for kubeadm config images -- 37.78s
kubernetes/master : kubeadm | Initialize first master ------------------ 26.95s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 24.83s
Install packages ------------------------------------------------------- 23.56s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.79s
Wait for host to be available ------------------------------------------ 16.49s
etcd : Gen_certs | Write etcd master certs ----------------------------- 13.12s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 12.34s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 11.95s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 11.86s
Extend root VG --------------------------------------------------------- 10.90s
etcd : reload etcd ----------------------------------------------------- 10.83s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.83s
container-engine/docker : Docker | pause while Docker restarts --------- 10.15s
download : file_download | Download item -------------------------------- 8.44s
etcd : wait for etcd up ------------------------------------------------- 7.67s
gather facts from all instances ----------------------------------------- 7.45s
kubernetes/master : kubeadm | write out kubeadm certs ------------------- 7.45s
==> 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