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

ci at centos.org ci at centos.org
Thu Dec 20 01:05:40 UTC 2018


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

------------------------------------------
[...truncated 575.48 KB...]
TASK [GCS Pre | Cluster ID | Generate a UUID] **********************************
Thursday 20 December 2018  00:53:40 +0000 (0:00:01.172)       0:16:35.772 ***** 
changed: [kube1]

TASK [GCS Pre | Cluster ID | Set gcs_gd2_clusterid fact] ***********************
Thursday 20 December 2018  00:53:41 +0000 (0:00:00.981)       0:16:36.754 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests directory | Create a temporary directory] ************
Thursday 20 December 2018  00:53:41 +0000 (0:00:00.499)       0:16:37.253 ***** 
changed: [kube1]

TASK [GCS Pre | Manifests directory | Set manifests_dir fact] ******************
Thursday 20 December 2018  00:53:42 +0000 (0:00:01.357)       0:16:38.611 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Sync GCS manifests] ********************************
Thursday 20 December 2018  00:53:43 +0000 (0:00:00.582)       0:16:39.194 ***** 
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] ******************************
Thursday 20 December 2018  00:54:06 +0000 (0:00:22.834)       0:17:02.029 ***** 
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] ***
Thursday 20 December 2018  00:54:06 +0000 (0:00:00.287)       0:17:02.317 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Thursday 20 December 2018  00:54:07 +0000 (0:00:00.533)       0:17:02.850 ***** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Thursday 20 December 2018  00:54:09 +0000 (0:00:02.098)       0:17:04.948 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Thursday 20 December 2018  00:54:09 +0000 (0:00:00.427)       0:17:05.376 ***** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Thursday 20 December 2018  00:54:11 +0000 (0:00:02.102)       0:17:07.479 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Thursday 20 December 2018  00:54:12 +0000 (0:00:00.434)       0:17:07.914 ***** 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Thursday 20 December 2018  00:54:14 +0000 (0:00:02.104)       0:17:10.018 ***** 
ok: [kube1]

TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Thursday 20 December 2018  00:54:15 +0000 (0:00:01.629)       0:17:11.648 ***** 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Thursday 20 December 2018  00:54:17 +0000 (0:00:01.514)       0:17:13.163 ***** 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Thursday 20 December 2018  00:54:19 +0000 (0:00:01.560)       0:17:14.724 ***** 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Thursday 20 December 2018  00:54:31 +0000 (0:00:12.344)       0:17:27.068 ***** 
FAILED - RETRYING: GCS | ETCD Cluster | Deploy etcd-cluster (5 retries left).
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Thursday 20 December 2018  00:54:39 +0000 (0:00:08.267)       0:17:35.336 ***** 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Thursday 20 December 2018  00:54:40 +0000 (0:00:01.256)       0:17:36.593 ***** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Thursday 20 December 2018  00:54:41 +0000 (0:00:00.345)       0:17:36.938 ***** 
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] *********************************
Thursday 20 December 2018  00:55:52 +0000 (0:01:11.458)       0:18:48.397 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Thursday 20 December 2018  00:55:54 +0000 (0:00:01.691)       0:18:50.089 ***** 
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] ******************************
Thursday 20 December 2018  00:55:54 +0000 (0:00:00.188)       0:18:50.278 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Thursday 20 December 2018  00:55:54 +0000 (0:00:00.340)       0:18:50.619 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 20 December 2018  00:55:56 +0000 (0:00:01.674)       0:18:52.294 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Thursday 20 December 2018  00:55:56 +0000 (0:00:00.368)       0:18:52.663 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Thursday 20 December 2018  00:55:58 +0000 (0:00:01.589)       0:18:54.252 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Thursday 20 December 2018  00:55:58 +0000 (0:00:00.317)       0:18:54.569 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Thursday 20 December 2018  00:56:01 +0000 (0:00:02.263)       0:18:56.833 ***** 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Thursday 20 December 2018  00:56:02 +0000 (0:00:01.415)       0:18:58.249 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Thursday 20 December 2018  00:56:02 +0000 (0:00:00.331)       0:18:58.580 ***** 
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.11.249:24007/v1/peers"}
	to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry

PLAY RECAP *********************************************************************
kube1                      : ok=378  changed=113  unreachable=0    failed=1   
kube2                      : ok=294  changed=91   unreachable=0    failed=0   
kube3                      : ok=254  changed=71   unreachable=0    failed=0   

Thursday 20 December 2018  01:05:40 +0000 (0:09:37.419)       0:28:36.000 ***** 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 577.42s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 71.46s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 47.94s
kubernetes/master : Master | wait for the apiserver to be running ------ 43.93s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 39.83s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.82s
Install packages ------------------------------------------------------- 30.25s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 22.84s
Wait for host to be available ------------------------------------------ 20.83s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.40s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 15.42s
kubernetes/master : Master | wait for kube-controller-manager ---------- 14.92s
download : file_download | Download item ------------------------------- 14.39s
gather facts from all instances ---------------------------------------- 13.81s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.10s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.34s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 11.33s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 11.08s
docker : Docker | pause while Docker restarts -------------------------- 10.41s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 8.86s
==> 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