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

ci at centos.org ci at centos.org
Tue Apr 2 01:07:43 UTC 2019


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

------------------------------------------
[...truncated 459.50 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-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] ******************************
Tuesday 02 April 2019  01:55:57 +0100 (0:00:34.687)       0:18:08.409 ********* 
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] ***
Tuesday 02 April 2019  01:55:58 +0100 (0:00:00.241)       0:18:08.651 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Tuesday 02 April 2019  01:55:58 +0100 (0:00:00.378)       0:18:09.030 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Tuesday 02 April 2019  01:56:00 +0100 (0:00:02.034)       0:18:11.064 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Tuesday 02 April 2019  01:56:00 +0100 (0:00:00.425)       0:18:11.490 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Tuesday 02 April 2019  01:56:03 +0100 (0:00:02.237)       0:18:13.727 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Tuesday 02 April 2019  01:56:03 +0100 (0:00:00.363)       0:18:14.090 ********* 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Tuesday 02 April 2019  01:56:05 +0100 (0:00:02.093)       0:18:16.183 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Tuesday 02 April 2019  01:56:07 +0100 (0:00:01.526)       0:18:17.710 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Tuesday 02 April 2019  01:56:08 +0100 (0:00:01.538)       0:18:19.249 ********* 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Tuesday 02 April 2019  01:56:20 +0100 (0:00:12.229)       0:18:31.478 ********* 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Tuesday 02 April 2019  01:56:22 +0100 (0:00:01.732)       0:18:33.211 ********* 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Tuesday 02 April 2019  01:56:24 +0100 (0:00:01.381)       0:18:34.592 ********* 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Tuesday 02 April 2019  01:56:25 +0100 (0:00:01.290)       0:18:35.882 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Tuesday 02 April 2019  01:56:26 +0100 (0:00:01.531)       0:18:37.414 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Tuesday 02 April 2019  01:56:28 +0100 (0:00:01.801)       0:18:39.216 ********* 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Tuesday 02 April 2019  01:56:29 +0100 (0:00:01.162)       0:18:40.378 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 02 April 2019  01:56:30 +0100 (0:00:00.328)       0:18:40.707 ********* 
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] *********************************
Tuesday 02 April 2019  01:57:54 +0100 (0:01:23.923)       0:20:04.630 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Tuesday 02 April 2019  01:57:55 +0100 (0:00:01.737)       0:20:06.368 ********* 
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] ******************************
Tuesday 02 April 2019  01:57:55 +0100 (0:00:00.196)       0:20:06.564 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Tuesday 02 April 2019  01:57:56 +0100 (0:00:00.348)       0:20:06.912 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 02 April 2019  01:57:57 +0100 (0:00:01.598)       0:20:08.511 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Tuesday 02 April 2019  01:57:58 +0100 (0:00:00.307)       0:20:08.818 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 02 April 2019  01:57:59 +0100 (0:00:01.706)       0:20:10.525 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Tuesday 02 April 2019  01:58:00 +0100 (0:00:00.370)       0:20:10.896 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Tuesday 02 April 2019  01:58:01 +0100 (0:00:01.540)       0:20:12.436 ********* 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Tuesday 02 April 2019  01:58:03 +0100 (0:00:01.434)       0:20:13.871 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 02 April 2019  01:58:03 +0100 (0:00:00.306)       0:20:14.178 ********* 
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.58.81: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   

Tuesday 02 April 2019  02:07:42 +0100 (0:09:39.277)       0:29:53.455 ********* 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 579.28s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 83.92s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.75s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 39.38s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 34.69s
download : container_download | download images for kubeadm config images -- 33.62s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.27s
Install packages ------------------------------------------------------- 31.15s
Wait for host to be available ------------------------------------------ 20.69s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.22s
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) -- 17.39s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.35s
gather facts from all instances ---------------------------------------- 13.30s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.99s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 12.55s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.23s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.38s
etcd : reload etcd ----------------------------------------------------- 10.43s
container-engine/docker : Docker | pause while Docker restarts --------- 10.39s
==> 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