[CI-results] Build failed in Jenkins: gluster_anteater_gcs #159
ci at centos.org
ci at centos.org
Mon May 6 01:07:49 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/159/display/redirect>
------------------------------------------
[...truncated 459.54 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] ******************************
Monday 06 May 2019 01:56:04 +0100 (0:00:35.546) 0:18:08.217 ************
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] ***
Monday 06 May 2019 01:56:05 +0100 (0:00:00.326) 0:18:08.543 ************
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Monday 06 May 2019 01:56:05 +0100 (0:00:00.449) 0:18:08.993 ************
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Monday 06 May 2019 01:56:07 +0100 (0:00:02.209) 0:18:11.203 ************
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Monday 06 May 2019 01:56:08 +0100 (0:00:00.432) 0:18:11.635 ************
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Monday 06 May 2019 01:56:10 +0100 (0:00:02.013) 0:18:13.649 ************
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Monday 06 May 2019 01:56:10 +0100 (0:00:00.448) 0:18:14.097 ************
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Monday 06 May 2019 01:56:12 +0100 (0:00:02.104) 0:18:16.201 ************
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Monday 06 May 2019 01:56:14 +0100 (0:00:01.602) 0:18:17.803 ************
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Monday 06 May 2019 01:56:16 +0100 (0:00:01.497) 0:18:19.301 ************
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Monday 06 May 2019 01:56:28 +0100 (0:00:12.355) 0:18:31.657 ************
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Monday 06 May 2019 01:56:29 +0100 (0:00:01.478) 0:18:33.136 ************
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Monday 06 May 2019 01:56:31 +0100 (0:00:01.327) 0:18:34.463 ************
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Monday 06 May 2019 01:56:32 +0100 (0:00:01.242) 0:18:35.706 ************
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Monday 06 May 2019 01:56:34 +0100 (0:00:01.562) 0:18:37.268 ************
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Monday 06 May 2019 01:56:35 +0100 (0:00:01.872) 0:18:39.141 ************
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Monday 06 May 2019 01:56:37 +0100 (0:00:01.154) 0:18:40.295 ************
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Monday 06 May 2019 01:56:37 +0100 (0:00:00.378) 0:18:40.674 ************
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] *********************************
Monday 06 May 2019 01:58:01 +0100 (0:01:23.699) 0:20:04.374 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Monday 06 May 2019 01:58:02 +0100 (0:00:01.629) 0:20:06.004 ************
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] ******************************
Monday 06 May 2019 01:58:02 +0100 (0:00:00.206) 0:20:06.211 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Monday 06 May 2019 01:58:03 +0100 (0:00:00.347) 0:20:06.558 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 06 May 2019 01:58:04 +0100 (0:00:01.658) 0:20:08.216 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Monday 06 May 2019 01:58:05 +0100 (0:00:00.352) 0:20:08.569 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 06 May 2019 01:58:06 +0100 (0:00:01.565) 0:20:10.134 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Monday 06 May 2019 01:58:07 +0100 (0:00:00.372) 0:20:10.507 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Monday 06 May 2019 01:58:08 +0100 (0:00:01.551) 0:20:12.059 ************
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Monday 06 May 2019 01:58:09 +0100 (0:00:01.148) 0:20:13.207 ************
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Monday 06 May 2019 01:58:10 +0100 (0:00:00.318) 0:20:13.526 ************
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.34.237: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
Monday 06 May 2019 02:07:48 +0100 (0:09:38.584) 0:29:52.110 ************
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.58s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 83.70s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.96s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.95s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.55s
Install packages ------------------------------------------------------- 32.85s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.82s
download : container_download | download images for kubeadm config images -- 32.20s
Wait for host to be available ------------------------------------------ 20.90s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.10s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.77s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.54s
gather facts from all instances ---------------------------------------- 13.64s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.13s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.11s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.36s
etcd : reload etcd ----------------------------------------------------- 12.02s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.14s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 10.71s
container-engine/docker : Docker | pause while Docker restarts --------- 10.41s
==> 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