[CI-results] Build failed in Jenkins: gluster_anteater_gcs #121
ci at centos.org
ci at centos.org
Fri Mar 29 00:57:25 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/121/display/redirect>
------------------------------------------
[...truncated 459.58 KB...]
changed: [kube1] => (item=gcs-namespace.yml)
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 29 March 2019 00:47:06 +0000 (0:00:12.097) 0:10:41.079 **********
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 29 March 2019 00:47:07 +0000 (0:00:00.090) 0:10:41.170 **********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Friday 29 March 2019 00:47:07 +0000 (0:00:00.209) 0:10:41.379 **********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Friday 29 March 2019 00:47:08 +0000 (0:00:00.799) 0:10:42.179 **********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Friday 29 March 2019 00:47:08 +0000 (0:00:00.206) 0:10:42.385 **********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Friday 29 March 2019 00:47:09 +0000 (0:00:00.804) 0:10:43.190 **********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Friday 29 March 2019 00:47:09 +0000 (0:00:00.214) 0:10:43.404 **********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Friday 29 March 2019 00:47:10 +0000 (0:00:00.798) 0:10:44.202 **********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Friday 29 March 2019 00:47:10 +0000 (0:00:00.700) 0:10:44.903 **********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Friday 29 March 2019 00:47:11 +0000 (0:00:00.760) 0:10:45.663 **********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Friday 29 March 2019 00:47:22 +0000 (0:00:10.904) 0:10:56.568 **********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Friday 29 March 2019 00:47:23 +0000 (0:00:00.717) 0:10:57.285 **********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Friday 29 March 2019 00:47:23 +0000 (0:00:00.559) 0:10:57.845 **********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Friday 29 March 2019 00:47:24 +0000 (0:00:00.534) 0:10:58.380 **********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Friday 29 March 2019 00:47:24 +0000 (0:00:00.743) 0:10:59.123 **********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Friday 29 March 2019 00:47:25 +0000 (0:00:00.967) 0:11:00.091 **********
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Friday 29 March 2019 00:47:31 +0000 (0:00:05.956) 0:11:06.047 **********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Friday 29 March 2019 00:47:32 +0000 (0:00:00.231) 0:11:06.279 **********
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Friday 29 March 2019 00:48:26 +0000 (0:00:54.712) 0:12:00.992 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Friday 29 March 2019 00:48:27 +0000 (0:00:00.776) 0:12:01.768 **********
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 29 March 2019 00:48:27 +0000 (0:00:00.101) 0:12:01.869 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Friday 29 March 2019 00:48:27 +0000 (0:00:00.144) 0:12:02.014 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Friday 29 March 2019 00:48:28 +0000 (0:00:00.666) 0:12:02.681 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Friday 29 March 2019 00:48:28 +0000 (0:00:00.161) 0:12:02.842 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Friday 29 March 2019 00:48:29 +0000 (0:00:00.944) 0:12:03.787 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Friday 29 March 2019 00:48:29 +0000 (0:00:00.143) 0:12:03.931 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Friday 29 March 2019 00:48:30 +0000 (0:00:00.761) 0:12:04.692 **********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Friday 29 March 2019 00:48:31 +0000 (0:00:00.544) 0:12:05.236 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Friday 29 March 2019 00:48:31 +0000 (0:00:00.158) 0:12:05.395 **********
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.3.206: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=320 changed=93 unreachable=0 failed=0
kube3 : ok=284 changed=78 unreachable=0 failed=0
Friday 29 March 2019 00:57:25 +0000 (0:08:53.823) 0:20:59.219 **********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 533.82s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 54.71s
download : container_download | download images for kubeadm config images -- 39.32s
kubernetes/master : kubeadm | Initialize first master ------------------ 26.50s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 24.86s
Install packages ------------------------------------------------------- 24.12s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.92s
Wait for host to be available ------------------------------------------ 16.39s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 13.51s
Extend root VG --------------------------------------------------------- 13.48s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 13.14s
etcd : Gen_certs | Write etcd master certs ----------------------------- 12.94s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 12.10s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.90s
etcd : reload etcd ----------------------------------------------------- 10.87s
container-engine/docker : Docker | pause while Docker restarts --------- 10.17s
kubernetes/node : Enable bridge-nf-call tables ------------------------- 10.15s
etcd : Configure | Check if etcd cluster is healthy --------------------- 8.08s
gather facts from all instances ----------------------------------------- 7.96s
etcd : wait for etcd up ------------------------------------------------- 7.83s
==> 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