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

ci at centos.org ci at centos.org
Mon Apr 29 01:07:57 UTC 2019


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

------------------------------------------
[...truncated 459.45 KB...]
changed: [kube1] => (item=gcs-namespace.yml)
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-fs-csi.yml)
changed: [kube1] => (item=gcs-storage-snapshot.yml)
changed: [kube1] => (item=gcs-virtblock-csi.yml)
changed: [kube1] => (item=gcs-storage-virtblock.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] ******************************
Monday 29 April 2019  01:56:22 +0100 (0:00:34.943)       0:18:27.389 ********** 
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] ***
Monday 29 April 2019  01:56:22 +0100 (0:00:00.287)       0:18:27.676 ********** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Monday 29 April 2019  01:56:23 +0100 (0:00:00.548)       0:18:28.225 ********** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Monday 29 April 2019  01:56:25 +0100 (0:00:02.209)       0:18:30.435 ********** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Monday 29 April 2019  01:56:25 +0100 (0:00:00.543)       0:18:30.979 ********** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Monday 29 April 2019  01:56:27 +0100 (0:00:02.133)       0:18:33.112 ********** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Monday 29 April 2019  01:56:28 +0100 (0:00:00.535)       0:18:33.648 ********** 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Monday 29 April 2019  01:56:30 +0100 (0:00:02.027)       0:18:35.676 ********** 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Monday 29 April 2019  01:56:31 +0100 (0:00:01.484)       0:18:37.160 ********** 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Monday 29 April 2019  01:56:33 +0100 (0:00:01.757)       0:18:38.918 ********** 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Monday 29 April 2019  01:56:45 +0100 (0:00:12.121)       0:18:51.040 ********** 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Monday 29 April 2019  01:56:47 +0100 (0:00:01.726)       0:18:52.766 ********** 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Monday 29 April 2019  01:56:48 +0100 (0:00:01.317)       0:18:54.084 ********** 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Monday 29 April 2019  01:56:50 +0100 (0:00:01.500)       0:18:55.584 ********** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Monday 29 April 2019  01:56:52 +0100 (0:00:01.951)       0:18:57.536 ********** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Monday 29 April 2019  01:56:54 +0100 (0:00:02.058)       0:18:59.595 ********** 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Monday 29 April 2019  01:56:55 +0100 (0:00:01.244)       0:19:00.839 ********** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Monday 29 April 2019  01:56:56 +0100 (0:00:00.442)       0:19:01.282 ********** 
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).
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Monday 29 April 2019  01:58:08 +0100 (0:01:12.653)       0:20:13.936 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Monday 29 April 2019  01:58:10 +0100 (0:00:01.726)       0:20:15.662 ********** 
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] ******************************
Monday 29 April 2019  01:58:10 +0100 (0:00:00.203)       0:20:15.866 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Monday 29 April 2019  01:58:11 +0100 (0:00:00.482)       0:20:16.348 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 29 April 2019  01:58:12 +0100 (0:00:01.678)       0:20:18.027 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Monday 29 April 2019  01:58:13 +0100 (0:00:00.451)       0:20:18.479 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 29 April 2019  01:58:14 +0100 (0:00:01.548)       0:20:20.028 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Monday 29 April 2019  01:58:15 +0100 (0:00:00.477)       0:20:20.506 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Monday 29 April 2019  01:58:16 +0100 (0:00:01.553)       0:20:22.059 ********** 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Monday 29 April 2019  01:58:18 +0100 (0:00:01.677)       0:20:23.737 ********** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Monday 29 April 2019  01:58:18 +0100 (0:00:00.332)       0:20:24.070 ********** 
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.22.33:24007/v1/peers"}
	to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry

PLAY RECAP *********************************************************************
kube1                      : ok=421  changed=119  unreachable=0    failed=1   
kube2                      : ok=320  changed=93   unreachable=0    failed=0   
kube3                      : ok=283  changed=78   unreachable=0    failed=0   

Monday 29 April 2019  02:07:57 +0100 (0:09:38.653)       0:30:02.724 ********** 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.65s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 72.65s
download : container_download | download images for kubeadm config images -- 48.56s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.93s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.01s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 34.94s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.43s
Install packages ------------------------------------------------------- 31.77s
Wait for host to be available ------------------------------------------ 20.82s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.52s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.99s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 15.90s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 14.44s
gather facts from all instances ---------------------------------------- 14.32s
etcd : reload etcd ----------------------------------------------------- 12.36s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.36s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.12s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.79s
download : file_download | Download item ------------------------------- 10.86s
etcd : wait for etcd up ------------------------------------------------ 10.55s
==> 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