[CI-results] Build failed in Jenkins: gluster_anteater_gcs #36
ci at centos.org
ci at centos.org
Wed Jan 2 00:54:55 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/36/display/redirect>
------------------------------------------
[...truncated 575.46 KB...]
TASK [GCS Pre | Cluster ID | Generate a UUID] **********************************
Wednesday 02 January 2019 00:44:25 +0000 (0:00:00.371) 0:09:19.589 *****
changed: [kube1]
TASK [GCS Pre | Cluster ID | Set gcs_gd2_clusterid fact] ***********************
Wednesday 02 January 2019 00:44:25 +0000 (0:00:00.384) 0:09:19.973 *****
ok: [kube1]
TASK [GCS Pre | Manifests directory | Create a temporary directory] ************
Wednesday 02 January 2019 00:44:25 +0000 (0:00:00.151) 0:09:20.125 *****
changed: [kube1]
TASK [GCS Pre | Manifests directory | Set manifests_dir fact] ******************
Wednesday 02 January 2019 00:44:26 +0000 (0:00:00.556) 0:09:20.682 *****
ok: [kube1]
TASK [GCS Pre | Manifests | Sync GCS manifests] ********************************
Wednesday 02 January 2019 00:44:26 +0000 (0:00:00.149) 0:09:20.831 *****
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] ******************************
Wednesday 02 January 2019 00:44:35 +0000 (0:00:08.919) 0:09:29.750 *****
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 02 January 2019 00:44:35 +0000 (0:00:00.094) 0:09:29.845 *****
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Wednesday 02 January 2019 00:44:35 +0000 (0:00:00.137) 0:09:29.982 *****
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Wednesday 02 January 2019 00:44:36 +0000 (0:00:00.724) 0:09:30.707 *****
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Wednesday 02 January 2019 00:44:36 +0000 (0:00:00.142) 0:09:30.850 *****
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Wednesday 02 January 2019 00:44:37 +0000 (0:00:00.732) 0:09:31.582 *****
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Wednesday 02 January 2019 00:44:37 +0000 (0:00:00.132) 0:09:31.715 *****
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Wednesday 02 January 2019 00:44:38 +0000 (0:00:00.711) 0:09:32.426 *****
ok: [kube1]
TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Wednesday 02 January 2019 00:44:38 +0000 (0:00:00.669) 0:09:33.096 *****
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Wednesday 02 January 2019 00:44:39 +0000 (0:00:00.654) 0:09:33.750 *****
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Wednesday 02 January 2019 00:44:40 +0000 (0:00:00.714) 0:09:34.465 *****
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Wednesday 02 January 2019 00:44:51 +0000 (0:00:11.453) 0:09:45.919 *****
FAILED - RETRYING: GCS | ETCD Cluster | Deploy etcd-cluster (5 retries left).
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Wednesday 02 January 2019 00:44:57 +0000 (0:00:06.424) 0:09:52.344 *****
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Wednesday 02 January 2019 00:44:58 +0000 (0:00:00.543) 0:09:52.888 *****
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Wednesday 02 January 2019 00:44:58 +0000 (0:00:00.147) 0:09:53.035 *****
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] *********************************
Wednesday 02 January 2019 00:45:57 +0000 (0:00:58.368) 0:10:51.404 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Wednesday 02 January 2019 00:45:57 +0000 (0:00:00.842) 0:10:52.247 *****
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 02 January 2019 00:45:57 +0000 (0:00:00.124) 0:10:52.371 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Wednesday 02 January 2019 00:45:58 +0000 (0:00:00.153) 0:10:52.524 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 02 January 2019 00:45:58 +0000 (0:00:00.745) 0:10:53.270 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Wednesday 02 January 2019 00:45:59 +0000 (0:00:00.154) 0:10:53.424 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Wednesday 02 January 2019 00:46:00 +0000 (0:00:01.054) 0:10:54.479 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Wednesday 02 January 2019 00:46:00 +0000 (0:00:00.136) 0:10:54.616 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Wednesday 02 January 2019 00:46:00 +0000 (0:00:00.733) 0:10:55.349 *****
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Wednesday 02 January 2019 00:46:01 +0000 (0:00:00.550) 0:10:55.899 *****
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Wednesday 02 January 2019 00:46:01 +0000 (0:00:00.295) 0:10:56.195 *****
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.52.219:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=379 changed=113 unreachable=0 failed=1
kube2 : ok=293 changed=91 unreachable=0 failed=0
kube3 : ok=254 changed=71 unreachable=0 failed=0
Wednesday 02 January 2019 00:54:54 +0000 (0:08:53.069) 0:19:49.265 *****
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 533.07s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 58.37s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 38.59s
kubernetes/master : Master | wait for the apiserver to be running ------ 29.22s
Install packages ------------------------------------------------------- 23.65s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 21.35s
Extend root VG --------------------------------------------------------- 16.90s
Wait for host to be available ------------------------------------------ 16.34s
etcd : Gen_certs | Write etcd master certs ----------------------------- 13.45s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 11.45s
download : file_download | Download item ------------------------------- 11.30s
etcd : reload etcd ----------------------------------------------------- 10.76s
docker : Docker | pause while Docker restarts -------------------------- 10.15s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 9.61s
GCS Pre | Manifests | Sync GCS manifests -------------------------------- 8.92s
gather facts from all instances ----------------------------------------- 8.55s
kubernetes/master : Master | wait for kube-controller-manager ----------- 8.38s
kubernetes/node : Ensure nodePort range is reserved --------------------- 8.11s
etcd : wait for etcd up ------------------------------------------------- 8.06s
kubernetes/master : Master | wait for kube-scheduler -------------------- 6.59s
==> 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