[CI-results] Build failed in Jenkins: gluster_anteater_gcs #20
ci at centos.org
ci at centos.org
Mon Dec 17 01:05:27 UTC 2018
See <https://ci.centos.org/job/gluster_anteater_gcs/20/display/redirect>
------------------------------------------
[...truncated 575.50 KB...]
TASK [GCS Pre | Cluster ID | Generate a UUID] **********************************
Monday 17 December 2018 00:53:29 +0000 (0:00:01.103) 0:16:10.159 *******
changed: [kube1]
TASK [GCS Pre | Cluster ID | Set gcs_gd2_clusterid fact] ***********************
Monday 17 December 2018 00:53:30 +0000 (0:00:01.015) 0:16:11.175 *******
ok: [kube1]
TASK [GCS Pre | Manifests directory | Create a temporary directory] ************
Monday 17 December 2018 00:53:30 +0000 (0:00:00.412) 0:16:11.587 *******
changed: [kube1]
TASK [GCS Pre | Manifests directory | Set manifests_dir fact] ******************
Monday 17 December 2018 00:53:32 +0000 (0:00:01.170) 0:16:12.758 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Sync GCS manifests] ********************************
Monday 17 December 2018 00:53:32 +0000 (0:00:00.384) 0:16:13.143 *******
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-csi.yml)
changed: [kube1] => (item=gcs-storage-snapshot.yml)
changed: [kube1] => (item=gcs-csi-node-info-crd.yml)
changed: [kube1] => (item=gcs-csi-driver-registry-crd.yml)
changed: [kube1] => (item=monitoring-namespace.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-grafana.yml)
TASK [GCS Pre | Manifests | Create GD2 manifests] ******************************
Monday 17 December 2018 00:53:55 +0000 (0:00:22.804) 0:16:35.947 *******
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 17 December 2018 00:53:55 +0000 (0:00:00.302) 0:16:36.250 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Monday 17 December 2018 00:53:56 +0000 (0:00:00.398) 0:16:36.648 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Monday 17 December 2018 00:53:57 +0000 (0:00:01.983) 0:16:38.632 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Monday 17 December 2018 00:53:58 +0000 (0:00:00.402) 0:16:39.034 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Monday 17 December 2018 00:54:00 +0000 (0:00:02.130) 0:16:41.165 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Monday 17 December 2018 00:54:00 +0000 (0:00:00.426) 0:16:41.591 *******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Monday 17 December 2018 00:54:03 +0000 (0:00:02.083) 0:16:43.675 *******
ok: [kube1]
TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Monday 17 December 2018 00:54:04 +0000 (0:00:01.603) 0:16:45.278 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Monday 17 December 2018 00:54:06 +0000 (0:00:01.665) 0:16:46.944 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Monday 17 December 2018 00:54:07 +0000 (0:00:01.665) 0:16:48.609 *******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Monday 17 December 2018 00:54:20 +0000 (0:00:12.362) 0:17:00.971 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Monday 17 December 2018 00:54:22 +0000 (0:00:02.083) 0:17:03.055 *******
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Monday 17 December 2018 00:54:29 +0000 (0:00:07.453) 0:17:10.509 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Monday 17 December 2018 00:54:30 +0000 (0:00:00.325) 0:17:10.835 *******
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Monday 17 December 2018 00:55:40 +0000 (0:01:10.244) 0:18:21.079 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Monday 17 December 2018 00:55:42 +0000 (0:00:01.702) 0:18:22.781 *******
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 17 December 2018 00:55:42 +0000 (0:00:00.213) 0:18:22.995 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Monday 17 December 2018 00:55:42 +0000 (0:00:00.311) 0:18:23.306 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 17 December 2018 00:55:44 +0000 (0:00:01.563) 0:18:24.869 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Monday 17 December 2018 00:55:44 +0000 (0:00:00.316) 0:18:25.186 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 17 December 2018 00:55:46 +0000 (0:00:01.617) 0:18:26.803 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Monday 17 December 2018 00:55:46 +0000 (0:00:00.346) 0:18:27.149 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Monday 17 December 2018 00:55:48 +0000 (0:00:01.526) 0:18:28.676 *******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Monday 17 December 2018 00:55:49 +0000 (0:00:01.475) 0:18:30.152 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Monday 17 December 2018 00:55:49 +0000 (0:00:00.317) 0:18:30.470 *******
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.59.234:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=378 changed=113 unreachable=0 failed=1
kube2 : ok=294 changed=91 unreachable=0 failed=0
kube3 : ok=254 changed=71 unreachable=0 failed=0
Monday 17 December 2018 01:05:26 +0000 (0:09:36.805) 0:28:07.276 *******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 576.81s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 70.24s
kubernetes/master : Master | wait for the apiserver to be running ------ 43.92s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.60s
kubernetes/master : Master | wait for kube-controller-manager ---------- 32.38s
Install packages ------------------------------------------------------- 30.30s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 28.08s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 22.80s
Wait for host to be available ------------------------------------------ 21.05s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 17.04s
download : file_download | Download item ------------------------------- 12.89s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.84s
gather facts from all instances ---------------------------------------- 12.48s
etcd : wait for etcd up ------------------------------------------------ 12.42s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.36s
etcd : reload etcd ----------------------------------------------------- 11.81s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 11.07s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 10.98s
docker : Docker | pause while Docker restarts -------------------------- 10.42s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------- 8.90s
==> 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