[CI-results] Build failed in Jenkins: gluster_anteater_gcs #106
ci at centos.org
ci at centos.org
Thu Mar 14 01:07:39 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/106/display/redirect>
------------------------------------------
[...truncated 459.58 KB...]
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] ******************************
Thursday 14 March 2019 00:55:37 +0000 (0:00:35.309) 0:18:16.817 ********
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] ***
Thursday 14 March 2019 00:55:37 +0000 (0:00:00.313) 0:18:17.130 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Thursday 14 March 2019 00:55:38 +0000 (0:00:00.448) 0:18:17.578 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Thursday 14 March 2019 00:55:40 +0000 (0:00:02.059) 0:18:19.638 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Thursday 14 March 2019 00:55:40 +0000 (0:00:00.439) 0:18:20.077 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Thursday 14 March 2019 00:55:42 +0000 (0:00:02.136) 0:18:22.214 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Thursday 14 March 2019 00:55:43 +0000 (0:00:00.420) 0:18:22.634 ********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Thursday 14 March 2019 00:55:45 +0000 (0:00:01.980) 0:18:24.615 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Thursday 14 March 2019 00:55:46 +0000 (0:00:01.436) 0:18:26.052 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Thursday 14 March 2019 00:55:48 +0000 (0:00:01.617) 0:18:27.669 ********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Thursday 14 March 2019 00:56:00 +0000 (0:00:12.100) 0:18:39.770 ********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Thursday 14 March 2019 00:56:01 +0000 (0:00:01.613) 0:18:41.383 ********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Thursday 14 March 2019 00:56:03 +0000 (0:00:01.286) 0:18:42.670 ********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Thursday 14 March 2019 00:56:04 +0000 (0:00:01.200) 0:18:43.870 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Thursday 14 March 2019 00:56:06 +0000 (0:00:01.692) 0:18:45.563 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Thursday 14 March 2019 00:56:08 +0000 (0:00:01.905) 0:18:47.468 ********
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Thursday 14 March 2019 00:56:15 +0000 (0:00:07.375) 0:18:54.844 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Thursday 14 March 2019 00:56:15 +0000 (0:00:00.351) 0:18:55.195 ********
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] *********************************
Thursday 14 March 2019 00:57:51 +0000 (0:01:35.554) 0:20:30.750 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Thursday 14 March 2019 00:57:53 +0000 (0:00:01.894) 0:20:32.645 ********
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] ******************************
Thursday 14 March 2019 00:57:53 +0000 (0:00:00.207) 0:20:32.853 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Thursday 14 March 2019 00:57:53 +0000 (0:00:00.397) 0:20:33.251 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 14 March 2019 00:57:55 +0000 (0:00:01.590) 0:20:34.842 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Thursday 14 March 2019 00:57:55 +0000 (0:00:00.316) 0:20:35.158 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 14 March 2019 00:57:57 +0000 (0:00:01.782) 0:20:36.941 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Thursday 14 March 2019 00:57:57 +0000 (0:00:00.370) 0:20:37.311 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Thursday 14 March 2019 00:57:59 +0000 (0:00:01.443) 0:20:38.755 ********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Thursday 14 March 2019 00:58:00 +0000 (0:00:01.413) 0:20:40.168 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Thursday 14 March 2019 00:58:01 +0000 (0:00:00.323) 0:20:40.492 ********
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.16.154: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
Thursday 14 March 2019 01:07:38 +0000 (0:09:37.667) 0:30:18.159 ********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 577.67s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 95.55s
download : container_download | download images for kubeadm config images -- 39.38s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.65s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.39s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.31s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.19s
Install packages ------------------------------------------------------- 31.10s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.75s
Wait for host to be available ------------------------------------------ 20.73s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 20.43s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.67s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.37s
gather facts from all instances ---------------------------------------- 13.26s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.61s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.10s
etcd : reload etcd ----------------------------------------------------- 11.90s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.42s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 10.93s
download : file_download | Download item ------------------------------- 10.60s
==> 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