[CI-results] Build failed in Jenkins: gluster_anteater_gcs #84
ci at centos.org
ci at centos.org
Wed Feb 20 12:05:31 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/84/display/redirect>
------------------------------------------
[...truncated 459.61 KB...]
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 20 February 2019 11:53:34 +0000 (0:00:35.725) 0:18:18.188 ****
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 20 February 2019 11:53:34 +0000 (0:00:00.290) 0:18:18.478 ****
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Wednesday 20 February 2019 11:53:35 +0000 (0:00:00.383) 0:18:18.861 ****
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Wednesday 20 February 2019 11:53:37 +0000 (0:00:02.038) 0:18:20.900 ****
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Wednesday 20 February 2019 11:53:37 +0000 (0:00:00.441) 0:18:21.342 ****
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Wednesday 20 February 2019 11:53:39 +0000 (0:00:02.126) 0:18:23.468 ****
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Wednesday 20 February 2019 11:53:40 +0000 (0:00:00.438) 0:18:23.906 ****
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Wednesday 20 February 2019 11:53:42 +0000 (0:00:02.122) 0:18:26.029 ****
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Wednesday 20 February 2019 11:53:43 +0000 (0:00:01.514) 0:18:27.544 ****
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Wednesday 20 February 2019 11:53:45 +0000 (0:00:01.592) 0:18:29.136 ****
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Wednesday 20 February 2019 11:53:57 +0000 (0:00:12.311) 0:18:41.447 ****
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Wednesday 20 February 2019 11:53:59 +0000 (0:00:01.633) 0:18:43.081 ****
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Wednesday 20 February 2019 11:54:00 +0000 (0:00:01.249) 0:18:44.331 ****
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Wednesday 20 February 2019 11:54:01 +0000 (0:00:01.143) 0:18:45.474 ****
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Wednesday 20 February 2019 11:54:03 +0000 (0:00:01.504) 0:18:46.979 ****
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Wednesday 20 February 2019 11:54:05 +0000 (0:00:01.829) 0:18:48.808 ****
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Wednesday 20 February 2019 11:54:06 +0000 (0:00:01.284) 0:18:50.093 ****
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Wednesday 20 February 2019 11:54:06 +0000 (0:00:00.327) 0:18:50.421 ****
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).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (43 retries left).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Wednesday 20 February 2019 11:55:42 +0000 (0:01:36.204) 0:20:26.626 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Wednesday 20 February 2019 11:55:44 +0000 (0:00:01.794) 0:20:28.421 ****
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 20 February 2019 11:55:45 +0000 (0:00:00.211) 0:20:28.632 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Wednesday 20 February 2019 11:55:45 +0000 (0:00:00.372) 0:20:29.004 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 20 February 2019 11:55:47 +0000 (0:00:01.647) 0:20:30.652 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Wednesday 20 February 2019 11:55:47 +0000 (0:00:00.351) 0:20:31.004 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 20 February 2019 11:55:49 +0000 (0:00:01.746) 0:20:32.751 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Wednesday 20 February 2019 11:55:49 +0000 (0:00:00.351) 0:20:33.103 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Wednesday 20 February 2019 11:55:51 +0000 (0:00:01.559) 0:20:34.662 ****
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Wednesday 20 February 2019 11:55:52 +0000 (0:00:01.425) 0:20:36.088 ****
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Wednesday 20 February 2019 11:55:52 +0000 (0:00:00.341) 0:20:36.430 ****
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.20.94: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
Wednesday 20 February 2019 12:05:31 +0000 (0:09:38.596) 0:30:15.026 ****
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.60s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 96.20s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 40.48s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.83s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.73s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.44s
download : container_download | download images for kubeadm config images -- 31.91s
Install packages ------------------------------------------------------- 30.47s
Wait for host to be available ------------------------------------------ 20.83s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.63s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.75s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.94s
gather facts from all instances ---------------------------------------- 13.65s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.52s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.33s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.31s
etcd : reload etcd ----------------------------------------------------- 11.91s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.50s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.33s
container-engine/docker : Docker | pause while Docker restarts --------- 10.40s
==> 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