[CI-results] Build failed in Jenkins: gluster_anteater_gcs #104
ci at centos.org
ci at centos.org
Tue Mar 12 01:07:32 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/104/display/redirect>
------------------------------------------
[...truncated 459.55 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 12 March 2019 00:55:48 +0000 (0:00:35.440) 0:18:10.026 *********
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 12 March 2019 00:55:48 +0000 (0:00:00.226) 0:18:10.253 *********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Tuesday 12 March 2019 00:55:48 +0000 (0:00:00.359) 0:18:10.612 *********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Tuesday 12 March 2019 00:55:50 +0000 (0:00:02.131) 0:18:12.744 *********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Tuesday 12 March 2019 00:55:51 +0000 (0:00:00.421) 0:18:13.165 *********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Tuesday 12 March 2019 00:55:53 +0000 (0:00:01.979) 0:18:15.145 *********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Tuesday 12 March 2019 00:55:53 +0000 (0:00:00.439) 0:18:15.585 *********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Tuesday 12 March 2019 00:55:55 +0000 (0:00:02.086) 0:18:17.672 *********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Tuesday 12 March 2019 00:55:57 +0000 (0:00:01.510) 0:18:19.182 *********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Tuesday 12 March 2019 00:55:58 +0000 (0:00:01.600) 0:18:20.783 *********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Tuesday 12 March 2019 00:56:11 +0000 (0:00:12.275) 0:18:33.058 *********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Tuesday 12 March 2019 00:56:12 +0000 (0:00:01.743) 0:18:34.802 *********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Tuesday 12 March 2019 00:56:14 +0000 (0:00:01.241) 0:18:36.043 *********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Tuesday 12 March 2019 00:56:15 +0000 (0:00:01.300) 0:18:37.344 *********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Tuesday 12 March 2019 00:56:17 +0000 (0:00:01.619) 0:18:38.964 *********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Tuesday 12 March 2019 00:56:18 +0000 (0:00:01.795) 0:18:40.760 *********
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Tuesday 12 March 2019 00:56:20 +0000 (0:00:01.074) 0:18:41.835 *********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 12 March 2019 00:56:20 +0000 (0:00:00.400) 0:18:42.235 *********
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 12 March 2019 00:57:44 +0000 (0:01:24.433) 0:20:06.669 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Tuesday 12 March 2019 00:57:46 +0000 (0:00:01.662) 0:20:08.331 *********
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 12 March 2019 00:57:46 +0000 (0:00:00.211) 0:20:08.543 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Tuesday 12 March 2019 00:57:47 +0000 (0:00:00.329) 0:20:08.872 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 12 March 2019 00:57:48 +0000 (0:00:01.613) 0:20:10.485 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Tuesday 12 March 2019 00:57:49 +0000 (0:00:00.338) 0:20:10.824 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 12 March 2019 00:57:50 +0000 (0:00:01.578) 0:20:12.402 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Tuesday 12 March 2019 00:57:50 +0000 (0:00:00.368) 0:20:12.771 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Tuesday 12 March 2019 00:57:52 +0000 (0:00:01.510) 0:20:14.281 *********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Tuesday 12 March 2019 00:57:54 +0000 (0:00:01.729) 0:20:16.011 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 12 March 2019 00:57:54 +0000 (0:00:00.344) 0:20:16.355 *********
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.27.60: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 12 March 2019 01:07:32 +0000 (0:09:37.580) 0:29:53.936 *********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 577.58s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.43s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.59s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.22s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.44s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.69s
download : container_download | download images for kubeadm config images -- 33.00s
Install packages ------------------------------------------------------- 29.83s
Wait for host to be available ------------------------------------------ 20.57s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.32s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 20.18s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 19.13s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.57s
gather facts from all instances ---------------------------------------- 13.03s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.87s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.28s
etcd : reload etcd ----------------------------------------------------- 11.90s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.32s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 10.87s
container-engine/docker : Docker | pause while Docker restarts --------- 10.41s
==> 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