[CI-results] Build failed in Jenkins: gluster_anteater_gcs #76
ci at centos.org
ci at centos.org
Mon Feb 11 00:55:43 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/76/display/redirect>
------------------------------------------
[...truncated 459.39 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] ******************************
Monday 11 February 2019 00:45:18 +0000 (0:00:11.954) 0:10:34.344 *******
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 11 February 2019 00:45:18 +0000 (0:00:00.099) 0:10:34.444 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Monday 11 February 2019 00:45:18 +0000 (0:00:00.218) 0:10:34.663 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Monday 11 February 2019 00:45:19 +0000 (0:00:00.819) 0:10:35.482 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Monday 11 February 2019 00:45:19 +0000 (0:00:00.206) 0:10:35.689 *******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Monday 11 February 2019 00:45:20 +0000 (0:00:00.787) 0:10:36.477 *******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Monday 11 February 2019 00:45:20 +0000 (0:00:00.206) 0:10:36.683 *******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Monday 11 February 2019 00:45:21 +0000 (0:00:00.811) 0:10:37.495 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Monday 11 February 2019 00:45:22 +0000 (0:00:00.708) 0:10:38.203 *******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Monday 11 February 2019 00:45:23 +0000 (0:00:00.736) 0:10:38.940 *******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Monday 11 February 2019 00:45:34 +0000 (0:00:10.920) 0:10:49.860 *******
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Monday 11 February 2019 00:45:34 +0000 (0:00:00.640) 0:10:50.500 *******
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Monday 11 February 2019 00:45:35 +0000 (0:00:00.457) 0:10:50.958 *******
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Monday 11 February 2019 00:45:35 +0000 (0:00:00.468) 0:10:51.426 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Monday 11 February 2019 00:45:36 +0000 (0:00:00.716) 0:10:52.143 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Monday 11 February 2019 00:45:37 +0000 (0:00:00.864) 0:10:53.007 *******
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (4 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Monday 11 February 2019 00:45:49 +0000 (0:00:11.894) 0:11:04.902 *******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Monday 11 February 2019 00:45:49 +0000 (0:00:00.149) 0:11:05.052 *******
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] *********************************
Monday 11 February 2019 00:46:43 +0000 (0:00:54.634) 0:11:59.687 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Monday 11 February 2019 00:46:44 +0000 (0:00:00.791) 0:12:00.478 *******
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 11 February 2019 00:46:44 +0000 (0:00:00.110) 0:12:00.588 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Monday 11 February 2019 00:46:44 +0000 (0:00:00.143) 0:12:00.732 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 11 February 2019 00:46:45 +0000 (0:00:00.674) 0:12:01.407 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Monday 11 February 2019 00:46:45 +0000 (0:00:00.149) 0:12:01.557 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 11 February 2019 00:46:46 +0000 (0:00:00.837) 0:12:02.395 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Monday 11 February 2019 00:46:46 +0000 (0:00:00.154) 0:12:02.550 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Monday 11 February 2019 00:46:47 +0000 (0:00:00.774) 0:12:03.324 *******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Monday 11 February 2019 00:46:48 +0000 (0:00:00.538) 0:12:03.863 *******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Monday 11 February 2019 00:46:48 +0000 (0:00:00.149) 0:12:04.012 *******
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.33:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=421 changed=119 unreachable=0 failed=1
kube2 : ok=320 changed=93 unreachable=0 failed=0
kube3 : ok=283 changed=78 unreachable=0 failed=0
Monday 11 February 2019 00:55:42 +0000 (0:08:54.779) 0:20:58.792 *******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 534.78s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 54.63s
download : container_download | download images for kubeadm config images -- 34.82s
kubernetes/master : kubeadm | Initialize first master ------------------ 27.95s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 24.91s
Install packages ------------------------------------------------------- 24.03s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.68s
Wait for host to be available ------------------------------------------ 16.44s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 13.73s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 13.41s
etcd : Gen_certs | Write etcd master certs ----------------------------- 13.08s
Extend root VG --------------------------------------------------------- 12.05s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 11.95s
GCS | ETCD Cluster | Get etcd-client service --------------------------- 11.89s
kubernetes/node : install | Copy hyperkube binary from download dir ---- 11.12s
etcd : reload etcd ----------------------------------------------------- 11.11s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.92s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 10.76s
container-engine/docker : Docker | pause while Docker restarts --------- 10.22s
gather facts from all instances ----------------------------------------- 8.34s
==> 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