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

ci at centos.org ci at centos.org
Sat Dec 15 01:05:27 UTC 2018


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

------------------------------------------
[...truncated 575.66 KB...]

TASK [GCS Pre | Cluster ID | Set gcs_gd2_clusterid fact] ***********************
Saturday 15 December 2018  00:52:52 +0000 (0:00:01.032)       0:15:44.880 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests directory | Create a temporary directory] ************
Saturday 15 December 2018  00:52:52 +0000 (0:00:00.327)       0:15:45.207 ***** 
changed: [kube1]

TASK [GCS Pre | Manifests directory | Set manifests_dir fact] ******************
Saturday 15 December 2018  00:52:53 +0000 (0:00:01.230)       0:15:46.438 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Sync GCS manifests] ********************************
Saturday 15 December 2018  00:52:54 +0000 (0:00:00.350)       0:15:46.788 ***** 
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] ******************************
Saturday 15 December 2018  00:53:16 +0000 (0:00:22.421)       0:16:09.210 ***** 
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 15 December 2018  00:53:17 +0000 (0:00:00.287)       0:16:09.498 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Saturday 15 December 2018  00:53:17 +0000 (0:00:00.434)       0:16:09.932 ***** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Saturday 15 December 2018  00:53:19 +0000 (0:00:02.044)       0:16:11.977 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Saturday 15 December 2018  00:53:19 +0000 (0:00:00.368)       0:16:12.345 ***** 
changed: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Saturday 15 December 2018  00:53:21 +0000 (0:00:02.049)       0:16:14.395 ***** 
ok: [kube1]

TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Saturday 15 December 2018  00:53:22 +0000 (0:00:00.409)       0:16:14.804 ***** 
changed: [kube1]

TASK [GCS | Namespace | Create GCS namespace] **********************************
Saturday 15 December 2018  00:53:24 +0000 (0:00:02.088)       0:16:16.894 ***** 
ok: [kube1]

TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Saturday 15 December 2018  00:53:26 +0000 (0:00:01.620)       0:16:18.514 ***** 
ok: [kube1]

TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Saturday 15 December 2018  00:53:27 +0000 (0:00:01.596)       0:16:20.110 ***** 
ok: [kube1]

TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Saturday 15 December 2018  00:53:29 +0000 (0:00:01.768)       0:16:21.879 ***** 
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]

TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Saturday 15 December 2018  00:53:41 +0000 (0:00:12.254)       0:16:34.133 ***** 
FAILED - RETRYING: GCS | ETCD Cluster | Deploy etcd-cluster (5 retries left).
ok: [kube1]

TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Saturday 15 December 2018  00:53:49 +0000 (0:00:08.242)       0:16:42.376 ***** 
changed: [kube1]

TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Saturday 15 December 2018  00:53:51 +0000 (0:00:01.310)       0:16:43.686 ***** 
ok: [kube1]

TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Saturday 15 December 2018  00:53:51 +0000 (0:00:00.392)       0:16:44.078 ***** 
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).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (44 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (43 retries left).
FAILED - RETRYING: GCS | ETCD Cluster | Wait for etcd-cluster to become ready (42 retries left).
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Saturday 15 December 2018  00:55:39 +0000 (0:01:47.531)       0:18:31.610 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Saturday 15 December 2018  00:55:40 +0000 (0:00:01.792)       0:18:33.403 ***** 
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 15 December 2018  00:55:41 +0000 (0:00:00.219)       0:18:33.623 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Saturday 15 December 2018  00:55:41 +0000 (0:00:00.394)       0:18:34.018 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 15 December 2018  00:55:43 +0000 (0:00:01.648)       0:18:35.666 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Saturday 15 December 2018  00:55:43 +0000 (0:00:00.463)       0:18:36.129 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 15 December 2018  00:55:45 +0000 (0:00:01.700)       0:18:37.830 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Saturday 15 December 2018  00:55:45 +0000 (0:00:00.489)       0:18:38.320 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Saturday 15 December 2018  00:55:47 +0000 (0:00:01.653)       0:18:39.973 ***** 
changed: [kube1]

TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Saturday 15 December 2018  00:55:49 +0000 (0:00:01.755)       0:18:41.728 ***** 
ok: [kube1]

TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Saturday 15 December 2018  00:55:49 +0000 (0:00:00.498)       0:18:42.227 ***** 
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.41.244: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   

Saturday 15 December 2018  01:05:27 +0000 (0:09:37.818)       0:28:20.045 ***** 
=============================================================================== 
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 577.82s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------ 107.53s
kubernetes/master : Master | wait for the apiserver to be running ------ 43.66s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.96s
Install packages ------------------------------------------------------- 30.26s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 29.39s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 22.42s
Wait for host to be available ------------------------------------------ 20.80s
kubernetes/master : Master | wait for kube-controller-manager ---------- 17.36s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 16.85s
gather facts from all instances ---------------------------------------- 13.83s
download : file_download | Download item ------------------------------- 12.91s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.47s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.25s
etcd : reload etcd ----------------------------------------------------- 11.58s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 11.24s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 10.85s
docker : Docker | pause while Docker restarts -------------------------- 10.44s
etcd : wait for etcd up ------------------------------------------------- 9.70s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests --- 8.84s
==> 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