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

ci at centos.org ci at centos.org
Fri May 10 01:07:53 UTC 2019


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

------------------------------------------
[...truncated 459.57 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] ******************************
Friday 10 May 2019  01:56:09 +0100 (0:00:35.596)       0:18:27.592 ************ 
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] ***
Friday 10 May 2019  01:56:09 +0100 (0:00:00.263)       0:18:27.856 ************ 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Friday 10 May 2019  01:56:10 +0100 (0:00:00.535)       0:18:28.392 ************ 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Friday 10 May 2019  01:56:12 +0100 (0:00:02.063)       0:18:30.455 ************ 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Friday 10 May 2019  01:56:12 +0100 (0:00:00.446)       0:18:30.902 ************ 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Friday 10 May 2019  01:56:14 +0100 (0:00:02.091)       0:18:32.994 ************ 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Friday 10 May 2019  01:56:15 +0100 (0:00:00.414)       0:18:33.409 ************ 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Friday 10 May 2019  01:56:17 +0100 (0:00:02.060)       0:18:35.470 ************ 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Friday 10 May 2019  01:56:18 +0100 (0:00:01.626)       0:18:37.097 ************ 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Friday 10 May 2019  01:56:20 +0100 (0:00:01.597)       0:18:38.694 ************ 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Friday 10 May 2019  01:56:32 +0100 (0:00:12.103)       0:18:50.798 ************ 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Friday 10 May 2019  01:56:34 +0100 (0:00:01.577)       0:18:52.376 ************ 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Friday 10 May 2019  01:56:35 +0100 (0:00:01.246)       0:18:53.623 ************ 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Friday 10 May 2019  01:56:36 +0100 (0:00:01.314)       0:18:54.938 ************ 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Friday 10 May 2019  01:56:38 +0100 (0:00:01.725)       0:18:56.663 ************ 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Friday 10 May 2019  01:56:40 +0100 (0:00:01.856)       0:18:58.519 ************ 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Friday 10 May 2019  01:56:41 +0100 (0:00:01.334)       0:18:59.854 ************ 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Friday 10 May 2019  01:56:41 +0100 (0:00:00.355)       0:19:00.210 ************ 
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] *********************************
Friday 10 May 2019  01:58:06 +0100 (0:01:24.155)       0:20:24.365 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Friday 10 May 2019  01:58:07 +0100 (0:00:01.609)       0:20:25.974 ************ 
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] ******************************
Friday 10 May 2019  01:58:07 +0100 (0:00:00.208)       0:20:26.183 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Friday 10 May 2019  01:58:08 +0100 (0:00:00.338)       0:20:26.521 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Friday 10 May 2019  01:58:09 +0100 (0:00:01.641)       0:20:28.162 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Friday 10 May 2019  01:58:10 +0100 (0:00:00.365)       0:20:28.528 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Friday 10 May 2019  01:58:11 +0100 (0:00:01.606)       0:20:30.135 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Friday 10 May 2019  01:58:12 +0100 (0:00:00.406)       0:20:30.541 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Friday 10 May 2019  01:58:13 +0100 (0:00:01.511)       0:20:32.053 ************ 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Friday 10 May 2019  01:58:14 +0100 (0:00:01.254)       0:20:33.308 ************ 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Friday 10 May 2019  01:58:15 +0100 (0:00:00.333)       0:20:33.642 ************ 
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.249:24007/v1/peers"}
	to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry

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

Friday 10 May 2019  02:07:53 +0100 (0:09:38.196)       0:30:11.838 ************ 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.20s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.16s
download : container_download | download images for kubeadm config images -- 49.38s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 39.38s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.32s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.60s
Install packages ------------------------------------------------------- 34.29s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.19s
Wait for host to be available ------------------------------------------ 32.05s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.88s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.88s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 17.36s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.66s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.05s
gather facts from all instances ---------------------------------------- 12.92s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.10s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.74s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.43s
container-engine/docker : Docker | pause while Docker restarts --------- 10.36s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 9.28s
==> 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