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

ci at centos.org ci at centos.org
Tue Mar 26 01:07:40 UTC 2019


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

------------------------------------------
[...truncated 459.25 KB...]
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-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 26 March 2019  00:56:05 +0000 (0:00:34.844)       0:18:19.061 ********* 
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 26 March 2019  00:56:05 +0000 (0:00:00.235)       0:18:19.297 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Tuesday 26 March 2019  00:56:06 +0000 (0:00:00.496)       0:18:19.794 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Tuesday 26 March 2019  00:56:08 +0000 (0:00:02.263)       0:18:22.058 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Tuesday 26 March 2019  00:56:08 +0000 (0:00:00.495)       0:18:22.554 ********* 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Tuesday 26 March 2019  00:56:11 +0000 (0:00:02.266)       0:18:24.820 ********* 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Tuesday 26 March 2019  00:56:11 +0000 (0:00:00.540)       0:18:25.361 ********* 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Tuesday 26 March 2019  00:56:13 +0000 (0:00:02.160)       0:18:27.521 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Tuesday 26 March 2019  00:56:15 +0000 (0:00:01.627)       0:18:29.149 ********* 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Tuesday 26 March 2019  00:56:17 +0000 (0:00:01.783)       0:18:30.933 ********* 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | Anthill | Register CRDs] *******************************************
Tuesday 26 March 2019  00:56:29 +0000 (0:00:12.134)       0:18:43.067 ********* 
ok: [kube1]

TASK [Wait for GlusterCluster CRD to be registered] ****************************
Tuesday 26 March 2019  00:56:31 +0000 (0:00:01.550)       0:18:44.617 ********* 
ok: [kube1]

TASK [Wait for GlusterNode CRD to be registered] *******************************
Tuesday 26 March 2019  00:56:32 +0000 (0:00:01.234)       0:18:45.852 ********* 
ok: [kube1]

TASK [GCS | Anthill | Deploy operator] *****************************************
Tuesday 26 March 2019  00:56:33 +0000 (0:00:01.220)       0:18:47.072 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Tuesday 26 March 2019  00:56:35 +0000 (0:00:01.662)       0:18:48.735 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Tuesday 26 March 2019  00:56:37 +0000 (0:00:01.859)       0:18:50.594 ********* 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Tuesday 26 March 2019  00:56:38 +0000 (0:00:01.296)       0:18:51.890 ********* 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Tuesday 26 March 2019  00:56:38 +0000 (0:00:00.321)       0:18:52.212 ********* 
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 26 March 2019  00:57:52 +0000 (0:01:13.429)       0:20:05.641 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Tuesday 26 March 2019  00:57:53 +0000 (0:00:01.676)       0:20:07.318 ********* 
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 26 March 2019  00:57:53 +0000 (0:00:00.208)       0:20:07.527 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Tuesday 26 March 2019  00:57:54 +0000 (0:00:00.321)       0:20:07.849 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 26 March 2019  00:57:55 +0000 (0:00:01.427)       0:20:09.276 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Tuesday 26 March 2019  00:57:56 +0000 (0:00:00.369)       0:20:09.645 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Tuesday 26 March 2019  00:57:57 +0000 (0:00:01.680)       0:20:11.326 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Tuesday 26 March 2019  00:57:58 +0000 (0:00:00.322)       0:20:11.649 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Tuesday 26 March 2019  00:57:59 +0000 (0:00:01.558)       0:20:13.208 ********* 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Tuesday 26 March 2019  00:58:00 +0000 (0:00:01.317)       0:20:14.526 ********* 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Tuesday 26 March 2019  00:58:01 +0000 (0:00:00.374)       0:20:14.900 ********* 
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.32.7: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 26 March 2019  01:07:39 +0000 (0:09:38.474)       0:29:53.374 ********* 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 578.47s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 73.43s
download : container_download | download images for kubeadm config images -- 44.32s
kubernetes/master : kubeadm | Init other uninitialized masters --------- 39.16s
kubernetes/master : kubeadm | Initialize first master ------------------ 39.09s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 34.84s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.79s
Install packages ------------------------------------------------------- 31.23s
kubernetes/master : kubeadm | write out kubeadm certs ------------------ 21.22s
Wait for host to be available ------------------------------------------ 21.05s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 19.27s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.50s
etcd : wait for etcd up ------------------------------------------------ 13.46s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.13s
kubernetes-apps/ansible : Kubernetes Apps | Start Resources ------------ 13.00s
gather facts from all instances ---------------------------------------- 12.66s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.13s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.59s
download : file_download | Download item ------------------------------- 11.00s
container-engine/docker : Docker | pause while Docker restarts --------- 10.41s
==> 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