[CI-results] Build failed in Jenkins: gluster_anteater_gcs #112
ci at centos.org
ci at centos.org
Wed Mar 20 01:08:58 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/112/display/redirect>
------------------------------------------
[...truncated 459.44 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] ******************************
Wednesday 20 March 2019 00:57:12 +0000 (0:00:34.868) 0:18:12.103 *******
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 March 2019 00:57:12 +0000 (0:00:00.416) 0:18:12.519 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Wednesday 20 March 2019 00:57:12 +0000 (0:00:00.399) 0:18:12.918 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Wednesday 20 March 2019 00:57:14 +0000 (0:00:02.032) 0:18:14.951 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Wednesday 20 March 2019 00:57:15 +0000 (0:00:00.420) 0:18:15.371 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Wednesday 20 March 2019 00:57:17 +0000 (0:00:02.195) 0:18:17.567 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Wednesday 20 March 2019 00:57:18 +0000 (0:00:00.420) 0:18:17.988 *******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Wednesday 20 March 2019 00:57:19 +0000 (0:00:01.944) 0:18:19.933 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Wednesday 20 March 2019 00:57:21 +0000 (0:00:01.534) 0:18:21.467 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Wednesday 20 March 2019 00:57:23 +0000 (0:00:01.720) 0:18:23.188 *******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Wednesday 20 March 2019 00:57:35 +0000 (0:00:12.099) 0:18:35.287 *******
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Wednesday 20 March 2019 00:57:36 +0000 (0:00:01.604) 0:18:36.892 *******
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Wednesday 20 March 2019 00:57:38 +0000 (0:00:01.312) 0:18:38.205 *******
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Wednesday 20 March 2019 00:57:40 +0000 (0:00:02.286) 0:18:40.491 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Wednesday 20 March 2019 00:57:42 +0000 (0:00:01.596) 0:18:42.087 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Wednesday 20 March 2019 00:57:44 +0000 (0:00:01.926) 0:18:44.014 *******
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Wednesday 20 March 2019 00:57:45 +0000 (0:00:01.159) 0:18:45.174 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Wednesday 20 March 2019 00:57:45 +0000 (0:00:00.437) 0:18:45.612 *******
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] *********************************
Wednesday 20 March 2019 00:59:10 +0000 (0:01:24.700) 0:20:10.312 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Wednesday 20 March 2019 00:59:11 +0000 (0:00:01.576) 0:20:11.889 *******
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 March 2019 00:59:12 +0000 (0:00:00.216) 0:20:12.105 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Wednesday 20 March 2019 00:59:12 +0000 (0:00:00.332) 0:20:12.438 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 20 March 2019 00:59:14 +0000 (0:00:01.710) 0:20:14.148 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Wednesday 20 March 2019 00:59:14 +0000 (0:00:00.352) 0:20:14.501 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 20 March 2019 00:59:16 +0000 (0:00:01.644) 0:20:16.145 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Wednesday 20 March 2019 00:59:16 +0000 (0:00:00.311) 0:20:16.457 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Wednesday 20 March 2019 00:59:18 +0000 (0:00:01.653) 0:20:18.110 *******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Wednesday 20 March 2019 00:59:19 +0000 (0:00:01.275) 0:20:19.385 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Wednesday 20 March 2019 00:59:19 +0000 (0:00:00.305) 0:20:19.691 *******
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.50.247: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
Wednesday 20 March 2019 01:08:58 +0000 (0:09:38.475) 0:29:58.166 *******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.48s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.70s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.66s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.77s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 34.87s
download : container_download | download images for kubeadm config images -- 34.39s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.90s
Install packages ------------------------------------------------------- 32.14s
Wait for host to be available ------------------------------------------ 32.11s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.33s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.80s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 17.27s
etcd : wait for etcd up ------------------------------------------------ 13.41s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.29s
gather facts from all instances ---------------------------------------- 12.71s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.57s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.10s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.36s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.18s
container-engine/docker : Docker | pause while Docker restarts --------- 10.43s
==> 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