[CI-results] Build failed in Jenkins: gluster_anteater_gcs #157
ci at centos.org
ci at centos.org
Sat May 4 00:55:30 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/157/display/redirect?page=changes>
Changes:
[dkhandel] Add jenkins job to run lcov on gluster-block nightly
[amarts] Add jenkins job to run lcov on gluster-block nightly (#58)
[dkhandel] Give executable permissions to gluster-block-lcov script
[dkhandel] Add epel repo on the duffy machines to get lcov package
[dkhandel] Install epel on duffy machines to get lcov package
[dkhandel] Add '-y' when installing packages on duffy centos machines
------------------------------------------
[...truncated 459.33 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] ******************************
Saturday 04 May 2019 01:45:01 +0100 (0:00:11.774) 0:10:25.205 **********
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] ***
Saturday 04 May 2019 01:45:01 +0100 (0:00:00.091) 0:10:25.297 **********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Saturday 04 May 2019 01:45:01 +0100 (0:00:00.162) 0:10:25.459 **********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Saturday 04 May 2019 01:45:02 +0100 (0:00:00.731) 0:10:26.191 **********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Saturday 04 May 2019 01:45:02 +0100 (0:00:00.154) 0:10:26.346 **********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Saturday 04 May 2019 01:45:03 +0100 (0:00:00.761) 0:10:27.107 **********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Saturday 04 May 2019 01:45:03 +0100 (0:00:00.138) 0:10:27.245 **********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Saturday 04 May 2019 01:45:04 +0100 (0:00:00.724) 0:10:27.970 **********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Saturday 04 May 2019 01:45:04 +0100 (0:00:00.635) 0:10:28.606 **********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Saturday 04 May 2019 01:45:05 +0100 (0:00:00.669) 0:10:29.276 **********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Saturday 04 May 2019 01:45:16 +0100 (0:00:10.862) 0:10:40.138 **********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Saturday 04 May 2019 01:45:17 +0100 (0:00:00.644) 0:10:40.782 **********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Saturday 04 May 2019 01:45:17 +0100 (0:00:00.456) 0:10:41.238 **********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Saturday 04 May 2019 01:45:18 +0100 (0:00:00.478) 0:10:41.716 **********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Saturday 04 May 2019 01:45:18 +0100 (0:00:00.672) 0:10:42.389 **********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Saturday 04 May 2019 01:45:19 +0100 (0:00:00.857) 0:10:43.246 **********
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Saturday 04 May 2019 01:45:25 +0100 (0:00:05.879) 0:10:49.126 **********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Saturday 04 May 2019 01:45:25 +0100 (0:00:00.138) 0:10:49.264 **********
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] *********************************
Saturday 04 May 2019 01:46:30 +0100 (0:01:05.094) 0:11:54.359 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Saturday 04 May 2019 01:46:31 +0100 (0:00:00.799) 0:11:55.159 **********
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] ******************************
Saturday 04 May 2019 01:46:31 +0100 (0:00:00.113) 0:11:55.272 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Saturday 04 May 2019 01:46:31 +0100 (0:00:00.139) 0:11:55.412 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 04 May 2019 01:46:32 +0100 (0:00:00.703) 0:11:56.115 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Saturday 04 May 2019 01:46:32 +0100 (0:00:00.165) 0:11:56.281 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 04 May 2019 01:46:33 +0100 (0:00:00.796) 0:11:57.078 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Saturday 04 May 2019 01:46:33 +0100 (0:00:00.184) 0:11:57.262 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Saturday 04 May 2019 01:46:34 +0100 (0:00:00.741) 0:11:58.004 **********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Saturday 04 May 2019 01:46:34 +0100 (0:00:00.524) 0:11:58.529 **********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Saturday 04 May 2019 01:46:35 +0100 (0:00:00.181) 0:11:58.710 **********
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.38.133: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
Saturday 04 May 2019 01:55:29 +0100 (0:08:54.750) 0:20:53.460 **********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 534.75s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 65.09s
download : container_download | download images for kubeadm config images -- 34.68s
kubernetes/master : kubeadm | Initialize first master ------------------ 28.82s
Install packages ------------------------------------------------------- 25.87s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 25.04s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 18.75s
Wait for host to be available ------------------------------------------ 16.53s
Extend root VG --------------------------------------------------------- 15.06s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 12.97s
etcd : Gen_certs | Write etcd master certs ----------------------------- 12.69s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 11.77s
etcd : reload etcd ----------------------------------------------------- 11.21s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.86s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 10.66s
container-engine/docker : Docker | pause while Docker restarts --------- 10.20s
kubernetes/node : install | Copy hyperkube binary from download dir ----- 9.14s
gather facts from all instances ----------------------------------------- 9.13s
etcd : wait for etcd up ------------------------------------------------- 8.25s
download : file_download | Download item -------------------------------- 7.71s
==> 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