[CI-results] Build failed in Jenkins: gluster_anteater_gcs #139
ci at centos.org
ci at centos.org
Tue Apr 16 01:10:01 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/139/display/redirect>
------------------------------------------
[...truncated 459.49 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] ******************************
Tuesday 16 April 2019 01:58:15 +0100 (0:00:35.003) 0:18:10.580 *********
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] ***
Tuesday 16 April 2019 01:58:16 +0100 (0:00:00.299) 0:18:10.880 *********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Tuesday 16 April 2019 01:58:16 +0100 (0:00:00.558) 0:18:11.438 *********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Tuesday 16 April 2019 01:58:18 +0100 (0:00:02.207) 0:18:13.645 *********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Tuesday 16 April 2019 01:58:19 +0100 (0:00:00.548) 0:18:14.195 *********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Tuesday 16 April 2019 01:58:21 +0100 (0:00:02.098) 0:18:16.293 *********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Tuesday 16 April 2019 01:58:22 +0100 (0:00:00.641) 0:18:16.935 *********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Tuesday 16 April 2019 01:58:24 +0100 (0:00:02.069) 0:18:19.005 *********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Tuesday 16 April 2019 01:58:26 +0100 (0:00:01.823) 0:18:20.829 *********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Tuesday 16 April 2019 01:58:27 +0100 (0:00:01.582) 0:18:22.411 *********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Tuesday 16 April 2019 01:58:39 +0100 (0:00:12.239) 0:18:34.650 *********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Tuesday 16 April 2019 01:58:41 +0100 (0:00:01.707) 0:18:36.358 *********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Tuesday 16 April 2019 01:58:42 +0100 (0:00:01.437) 0:18:37.795 *********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Tuesday 16 April 2019 01:58:44 +0100 (0:00:01.320) 0:18:39.116 *********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Tuesday 16 April 2019 01:58:45 +0100 (0:00:01.618) 0:18:40.735 *********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Tuesday 16 April 2019 01:58:47 +0100 (0:00:02.011) 0:18:42.747 *********
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Tuesday 16 April 2019 01:58:49 +0100 (0:00:01.309) 0:18:44.056 *********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 16 April 2019 01:58:49 +0100 (0:00:00.481) 0:18:44.538 *********
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] *********************************
Tuesday 16 April 2019 02:00:13 +0100 (0:01:24.056) 0:20:08.594 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Tuesday 16 April 2019 02:00:15 +0100 (0:00:01.635) 0:20:10.230 *********
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] ******************************
Tuesday 16 April 2019 02:00:15 +0100 (0:00:00.195) 0:20:10.425 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Tuesday 16 April 2019 02:00:15 +0100 (0:00:00.351) 0:20:10.776 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 16 April 2019 02:00:17 +0100 (0:00:01.629) 0:20:12.406 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Tuesday 16 April 2019 02:00:17 +0100 (0:00:00.317) 0:20:12.723 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 16 April 2019 02:00:19 +0100 (0:00:01.635) 0:20:14.359 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Tuesday 16 April 2019 02:00:19 +0100 (0:00:00.314) 0:20:14.673 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Tuesday 16 April 2019 02:00:21 +0100 (0:00:01.473) 0:20:16.148 *********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Tuesday 16 April 2019 02:00:22 +0100 (0:00:01.377) 0:20:17.525 *********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 16 April 2019 02:00:23 +0100 (0:00:00.446) 0:20:17.972 *********
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.61.44: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
Tuesday 16 April 2019 02:10:01 +0100 (0:09:38.486) 0:29:56.458 *********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.49s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 84.06s
kubernetes/master : kubeadm | Initialize first master ------------------ 38.51s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 38.02s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 35.00s
download : container_download | download images for kubeadm config images -- 34.66s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.49s
Install packages ------------------------------------------------------- 31.28s
Wait for host to be available ------------------------------------------ 20.69s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 20.68s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.43s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 18.83s
gather facts from all instances ---------------------------------------- 14.36s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.47s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.80s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.24s
etcd : reload etcd ----------------------------------------------------- 11.95s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 11.95s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.75s
container-engine/docker : Docker | pause while Docker restarts --------- 10.38s
==> 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