[CI-results] Build failed in Jenkins: gluster_anteater_gcs #61
ci at centos.org
ci at centos.org
Sun Jan 27 01:07:29 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/61/display/redirect>
------------------------------------------
[...truncated 458.28 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-csi.yml)
changed: [kube1] => (item=gcs-storage-snapshot.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] ******************************
Sunday 27 January 2019 00:55:19 +0000 (0:00:31.544) 0:17:41.871 ********
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] ***
Sunday 27 January 2019 00:55:19 +0000 (0:00:00.241) 0:17:42.112 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Sunday 27 January 2019 00:55:20 +0000 (0:00:00.549) 0:17:42.662 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Sunday 27 January 2019 00:55:22 +0000 (0:00:02.303) 0:17:44.965 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Sunday 27 January 2019 00:55:22 +0000 (0:00:00.528) 0:17:45.493 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Sunday 27 January 2019 00:55:25 +0000 (0:00:02.175) 0:17:47.669 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Sunday 27 January 2019 00:55:25 +0000 (0:00:00.539) 0:17:48.209 ********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Sunday 27 January 2019 00:55:27 +0000 (0:00:01.997) 0:17:50.206 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Sunday 27 January 2019 00:55:29 +0000 (0:00:01.660) 0:17:51.867 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Sunday 27 January 2019 00:55:31 +0000 (0:00:01.748) 0:17:53.616 ********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Sunday 27 January 2019 00:55:44 +0000 (0:00:13.319) 0:18:06.936 ********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Sunday 27 January 2019 00:55:46 +0000 (0:00:01.750) 0:18:08.687 ********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Sunday 27 January 2019 00:55:47 +0000 (0:00:01.412) 0:18:10.100 ********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Sunday 27 January 2019 00:55:48 +0000 (0:00:01.246) 0:18:11.346 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Sunday 27 January 2019 00:55:50 +0000 (0:00:01.903) 0:18:13.249 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Sunday 27 January 2019 00:55:52 +0000 (0:00:02.104) 0:18:15.354 ********
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Sunday 27 January 2019 00:55:53 +0000 (0:00:01.191) 0:18:16.545 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Sunday 27 January 2019 00:55:54 +0000 (0:00:00.491) 0:18:17.037 ********
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).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (42 retries left).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Sunday 27 January 2019 00:57:41 +0000 (0:01:47.307) 0:20:04.345 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Sunday 27 January 2019 00:57:43 +0000 (0:00:01.822) 0:20:06.168 ********
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] ******************************
Sunday 27 January 2019 00:57:43 +0000 (0:00:00.192) 0:20:06.360 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Sunday 27 January 2019 00:57:44 +0000 (0:00:00.449) 0:20:06.810 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Sunday 27 January 2019 00:57:45 +0000 (0:00:01.654) 0:20:08.464 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Sunday 27 January 2019 00:57:46 +0000 (0:00:00.436) 0:20:08.900 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Sunday 27 January 2019 00:57:48 +0000 (0:00:01.778) 0:20:10.679 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Sunday 27 January 2019 00:57:48 +0000 (0:00:00.460) 0:20:11.139 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Sunday 27 January 2019 00:57:50 +0000 (0:00:01.668) 0:20:12.808 ********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Sunday 27 January 2019 00:57:51 +0000 (0:00:01.324) 0:20:14.133 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Sunday 27 January 2019 00:57:51 +0000 (0:00:00.361) 0:20:14.494 ********
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.62.71:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=416 changed=115 unreachable=0 failed=1
kube2 : ok=319 changed=91 unreachable=0 failed=0
kube3 : ok=281 changed=77 unreachable=0 failed=0
Sunday 27 January 2019 01:07:29 +0000 (0:09:37.516) 0:29:52.011 ********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 577.52s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------ 107.31s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.64s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.18s
download : container_download | download images for kubeadm config images -- 33.53s
etcd : Gen_certs | Write etcd master certs ----------------------------- 33.18s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 31.54s
Install packages ------------------------------------------------------- 29.15s
Wait for host to be available ------------------------------------------ 21.05s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.54s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.95s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.31s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 13.32s
gather facts from all instances ---------------------------------------- 13.21s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.04s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.62s
etcd : reload etcd ----------------------------------------------------- 11.85s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.19s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.09s
container-engine/docker : Docker | pause while Docker restarts --------- 10.39s
==> 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