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

ci at centos.org ci at centos.org
Wed May 15 01:07:14 UTC 2019


See <https://ci.centos.org/job/gluster_anteater_gcs/168/display/redirect?page=changes>

Changes:

[amarts] nightly-builds: fix shallow cloning of git repository for non-master

[amarts] nightly-builds: create a VERSION file to not need tags in the git repo

[amarts] gluster-blockd: configure without tirpc on CentOS (#60)

------------------------------------------
[...truncated 459.54 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] ******************************
Wednesday 15 May 2019  01:55:32 +0100 (0:00:34.996)       0:18:03.998 ********* 
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] ***
Wednesday 15 May 2019  01:55:32 +0100 (0:00:00.247)       0:18:04.245 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Wednesday 15 May 2019  01:55:32 +0100 (0:00:00.409)       0:18:04.655 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Wednesday 15 May 2019  01:55:34 +0100 (0:00:02.081)       0:18:06.737 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Wednesday 15 May 2019  01:55:35 +0100 (0:00:00.383)       0:18:07.120 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Wednesday 15 May 2019  01:55:37 +0100 (0:00:02.135)       0:18:09.256 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Wednesday 15 May 2019  01:55:37 +0100 (0:00:00.384)       0:18:09.640 ********* 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Wednesday 15 May 2019  01:55:39 +0100 (0:00:01.983)       0:18:11.623 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Wednesday 15 May 2019  01:55:41 +0100 (0:00:01.616)       0:18:13.240 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Wednesday 15 May 2019  01:55:43 +0100 (0:00:01.763)       0:18:15.004 ********* 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Wednesday 15 May 2019  01:55:55 +0100 (0:00:12.069)       0:18:27.073 ********* 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Wednesday 15 May 2019  01:55:56 +0100 (0:00:01.545)       0:18:28.619 ********* 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Wednesday 15 May 2019  01:55:57 +0100 (0:00:01.195)       0:18:29.815 ********* 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Wednesday 15 May 2019  01:55:59 +0100 (0:00:01.258)       0:18:31.074 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Wednesday 15 May 2019  01:56:00 +0100 (0:00:01.614)       0:18:32.688 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Wednesday 15 May 2019  01:56:02 +0100 (0:00:01.914)       0:18:34.602 ********* 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Wednesday 15 May 2019  01:56:03 +0100 (0:00:01.181)       0:18:35.784 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Wednesday 15 May 2019  01:56:04 +0100 (0:00:00.350)       0:18:36.135 ********* 
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] *********************************
Wednesday 15 May 2019  01:57:28 +0100 (0:01:24.095)       0:20:00.230 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Wednesday 15 May 2019  01:57:29 +0100 (0:00:01.526)       0:20:01.757 ********* 
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] ******************************
Wednesday 15 May 2019  01:57:30 +0100 (0:00:00.204)       0:20:01.961 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Wednesday 15 May 2019  01:57:30 +0100 (0:00:00.348)       0:20:02.310 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 15 May 2019  01:57:31 +0100 (0:00:01.440)       0:20:03.751 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Wednesday 15 May 2019  01:57:32 +0100 (0:00:00.400)       0:20:04.151 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 15 May 2019  01:57:33 +0100 (0:00:01.715)       0:20:05.867 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Wednesday 15 May 2019  01:57:34 +0100 (0:00:00.301)       0:20:06.169 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Wednesday 15 May 2019  01:57:35 +0100 (0:00:01.509)       0:20:07.678 ********* 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Wednesday 15 May 2019  01:57:36 +0100 (0:00:01.238)       0:20:08.917 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Wednesday 15 May 2019  01:57:37 +0100 (0:00:00.295)       0:20:09.213 ********* 
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.242: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   

Wednesday 15 May 2019  02:07:14 +0100 (0:09:36.881)       0:29:46.094 ********* 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 576.88s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.10s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.48s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.93s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.00s
download : container_download | download images for kubeadm config images -- 33.63s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.94s
Install packages ------------------------------------------------------- 32.29s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.64s
Wait for host to be available ------------------------------------------ 20.53s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.70s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 15.88s
gather facts from all instances ---------------------------------------- 14.04s
etcd : wait for etcd up ------------------------------------------------ 13.43s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.31s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.10s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.07s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.77s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.31s
container-engine/docker : Docker | pause while Docker restarts --------- 10.37s
==> 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