[CI-results] Build failed in Jenkins: gluster_anteater_gcs #132

ci at centos.org ci at centos.org
Tue Apr 9 00:56:34 UTC 2019


See <https://ci.centos.org/job/gluster_anteater_gcs/132/display/redirect>

------------------------------------------
[...truncated 459.49 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] ******************************
Tuesday 09 April 2019  01:46:04 +0100 (0:00:11.933)       0:10:20.937 ********* 
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 09 April 2019  01:46:04 +0100 (0:00:00.087)       0:10:21.025 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Tuesday 09 April 2019  01:46:04 +0100 (0:00:00.219)       0:10:21.244 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Tuesday 09 April 2019  01:46:05 +0100 (0:00:00.787)       0:10:22.031 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Tuesday 09 April 2019  01:46:05 +0100 (0:00:00.220)       0:10:22.252 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Tuesday 09 April 2019  01:46:06 +0100 (0:00:00.821)       0:10:23.073 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Tuesday 09 April 2019  01:46:06 +0100 (0:00:00.215)       0:10:23.289 ********* 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Tuesday 09 April 2019  01:46:07 +0100 (0:00:00.810)       0:10:24.100 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Tuesday 09 April 2019  01:46:08 +0100 (0:00:00.732)       0:10:24.832 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Tuesday 09 April 2019  01:46:09 +0100 (0:00:00.754)       0:10:25.586 ********* 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Tuesday 09 April 2019  01:46:20 +0100 (0:00:10.918)       0:10:36.505 ********* 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Tuesday 09 April 2019  01:46:20 +0100 (0:00:00.721)       0:10:37.227 ********* 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Tuesday 09 April 2019  01:46:21 +0100 (0:00:00.527)       0:10:37.754 ********* 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Tuesday 09 April 2019  01:46:22 +0100 (0:00:00.558)       0:10:38.313 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Tuesday 09 April 2019  01:46:22 +0100 (0:00:00.777)       0:10:39.091 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Tuesday 09 April 2019  01:46:23 +0100 (0:00:00.923)       0:10:40.014 ********* 
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Tuesday 09 April 2019  01:46:29 +0100 (0:00:05.947)       0:10:45.962 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 09 April 2019  01:46:29 +0100 (0:00:00.232)       0:10:46.194 ********* 
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] *********************************
Tuesday 09 April 2019  01:47:35 +0100 (0:01:05.321)       0:11:51.516 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Tuesday 09 April 2019  01:47:36 +0100 (0:00:00.791)       0:11:52.308 ********* 
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 09 April 2019  01:47:36 +0100 (0:00:00.102)       0:11:52.410 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Tuesday 09 April 2019  01:47:36 +0100 (0:00:00.152)       0:11:52.563 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 09 April 2019  01:47:36 +0100 (0:00:00.698)       0:11:53.261 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Tuesday 09 April 2019  01:47:37 +0100 (0:00:00.149)       0:11:53.411 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 09 April 2019  01:47:38 +0100 (0:00:00.894)       0:11:54.306 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Tuesday 09 April 2019  01:47:38 +0100 (0:00:00.148)       0:11:54.454 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Tuesday 09 April 2019  01:47:38 +0100 (0:00:00.724)       0:11:55.178 ********* 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Tuesday 09 April 2019  01:47:39 +0100 (0:00:00.527)       0:11:55.706 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 09 April 2019  01:47:39 +0100 (0:00:00.171)       0:11:55.877 ********* 
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.10.221: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   

Tuesday 09 April 2019  01:56:33 +0100 (0:08:54.327)       0:20:50.205 ********* 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 534.33s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 65.32s
download : container_download | download images for kubeadm config images -- 35.68s
kubernetes/master : kubeadm | Initialize first master ------------------ 28.70s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 24.37s
Install packages ------------------------------------------------------- 23.91s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 20.02s
Wait for host to be available ------------------------------------------ 16.40s
Extend root VG --------------------------------------------------------- 15.28s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 14.17s
etcd : Gen_certs | Write etcd master certs ----------------------------- 13.37s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 11.93s
etcd : reload etcd ----------------------------------------------------- 11.03s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.92s
container-engine/docker : Docker | pause while Docker restarts --------- 10.25s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 9.71s
gather facts from all instances ----------------------------------------- 8.61s
etcd : wait for etcd up ------------------------------------------------- 7.85s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests --- 7.64s
download : file_download | Download item -------------------------------- 7.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