[CI-results] Build failed in Jenkins: gluster_anteater_gcs #21
ci at centos.org
ci at centos.org
Tue Dec 18 01:08:15 UTC 2018
See <https://ci.centos.org/job/gluster_anteater_gcs/21/display/redirect>
------------------------------------------
[...truncated 575.49 KB...]
TASK [GCS Pre | Cluster ID | Generate a UUID] **********************************
Tuesday 18 December 2018 00:57:39 +0000 (0:00:00.449) 0:09:22.445 ******
changed: [kube1]
TASK [GCS Pre | Cluster ID | Set gcs_gd2_clusterid fact] ***********************
Tuesday 18 December 2018 00:57:39 +0000 (0:00:00.428) 0:09:22.873 ******
ok: [kube1]
TASK [GCS Pre | Manifests directory | Create a temporary directory] ************
Tuesday 18 December 2018 00:57:40 +0000 (0:00:00.226) 0:09:23.099 ******
changed: [kube1]
TASK [GCS Pre | Manifests directory | Set manifests_dir fact] ******************
Tuesday 18 December 2018 00:57:40 +0000 (0:00:00.570) 0:09:23.670 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Sync GCS manifests] ********************************
Tuesday 18 December 2018 00:57:40 +0000 (0:00:00.203) 0:09:23.873 ******
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] ******************************
Tuesday 18 December 2018 00:57:49 +0000 (0:00:08.926) 0:09:32.800 ******
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 18 December 2018 00:57:49 +0000 (0:00:00.093) 0:09:32.893 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Tuesday 18 December 2018 00:57:50 +0000 (0:00:00.206) 0:09:33.099 ******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Tuesday 18 December 2018 00:57:50 +0000 (0:00:00.782) 0:09:33.882 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Tuesday 18 December 2018 00:57:51 +0000 (0:00:00.226) 0:09:34.108 ******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Tuesday 18 December 2018 00:57:51 +0000 (0:00:00.816) 0:09:34.925 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Tuesday 18 December 2018 00:57:52 +0000 (0:00:00.224) 0:09:35.150 ******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Tuesday 18 December 2018 00:57:52 +0000 (0:00:00.850) 0:09:36.000 ******
ok: [kube1]
TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Tuesday 18 December 2018 00:57:53 +0000 (0:00:00.657) 0:09:36.658 ******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Tuesday 18 December 2018 00:57:54 +0000 (0:00:00.637) 0:09:37.296 ******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Tuesday 18 December 2018 00:57:54 +0000 (0:00:00.717) 0:09:38.013 ******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Tuesday 18 December 2018 00:58:05 +0000 (0:00:10.911) 0:09:48.925 ******
FAILED - RETRYING: GCS | ETCD Cluster | Deploy etcd-cluster (5 retries left).
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Tuesday 18 December 2018 00:58:12 +0000 (0:00:06.397) 0:09:55.323 ******
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Tuesday 18 December 2018 00:58:18 +0000 (0:00:05.902) 0:10:01.225 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 18 December 2018 00:58:18 +0000 (0:00:00.144) 0:10:01.370 ******
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Tuesday 18 December 2018 00:59:11 +0000 (0:00:53.426) 0:10:54.797 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Tuesday 18 December 2018 00:59:12 +0000 (0:00:00.983) 0:10:55.780 ******
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 18 December 2018 00:59:12 +0000 (0:00:00.099) 0:10:55.879 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Tuesday 18 December 2018 00:59:12 +0000 (0:00:00.148) 0:10:56.028 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 18 December 2018 00:59:13 +0000 (0:00:00.701) 0:10:56.729 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Tuesday 18 December 2018 00:59:13 +0000 (0:00:00.149) 0:10:56.879 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 18 December 2018 00:59:14 +0000 (0:00:00.850) 0:10:57.730 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Tuesday 18 December 2018 00:59:14 +0000 (0:00:00.146) 0:10:57.876 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Tuesday 18 December 2018 00:59:15 +0000 (0:00:00.861) 0:10:58.737 ******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Tuesday 18 December 2018 00:59:16 +0000 (0:00:00.653) 0:10:59.391 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 18 December 2018 00:59:16 +0000 (0:00:00.187) 0:10:59.579 ******
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.54.185: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
Tuesday 18 December 2018 01:08:15 +0000 (0:08:58.730) 0:19:58.309 ******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 538.73s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 53.43s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 41.68s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 30.55s
kubernetes/master : Master | wait for the apiserver to be running ------ 28.38s
Install packages ------------------------------------------------------- 23.79s
Wait for host to be available ------------------------------------------ 16.38s
Extend root VG --------------------------------------------------------- 15.63s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 13.99s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 13.86s
etcd : Gen_certs | Write etcd master certs ----------------------------- 13.09s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.91s
download : file_download | Download item ------------------------------- 10.81s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 10.46s
docker : Docker | pause while Docker restarts -------------------------- 10.15s
GCS Pre | Manifests | Sync GCS manifests -------------------------------- 8.93s
etcd : reload etcd ------------------------------------------------------ 8.36s
gather facts from all instances ----------------------------------------- 7.82s
kubernetes/master : Master | wait for kube-controller-manager ----------- 7.39s
GCS | ETCD Cluster | Deploy etcd-cluster -------------------------------- 6.40s
==> 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