[CI-results] Build failed in Jenkins: gluster_anteater_gcs #41
ci at centos.org
ci at centos.org
Mon Jan 7 01:05:38 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/41/display/redirect>
------------------------------------------
[...truncated 576.51 KB...]
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)
changed: [kube1] => (item=gcs-operator-crd.yml)
changed: [kube1] => (item=gcs-operator.yml)
TASK [GCS Pre | Manifests | Create GD2 manifests] ******************************
Monday 07 January 2019 00:53:28 +0000 (0:00:26.173) 0:16:27.523 ********
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 07 January 2019 00:53:28 +0000 (0:00:00.262) 0:16:27.785 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Monday 07 January 2019 00:53:29 +0000 (0:00:00.529) 0:16:28.314 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Monday 07 January 2019 00:53:31 +0000 (0:00:02.064) 0:16:30.379 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Monday 07 January 2019 00:53:31 +0000 (0:00:00.494) 0:16:30.874 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Monday 07 January 2019 00:53:33 +0000 (0:00:02.223) 0:16:33.097 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Monday 07 January 2019 00:53:34 +0000 (0:00:00.503) 0:16:33.601 ********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Monday 07 January 2019 00:53:36 +0000 (0:00:02.207) 0:16:35.808 ********
ok: [kube1]
TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Monday 07 January 2019 00:53:38 +0000 (0:00:01.747) 0:16:37.556 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Monday 07 January 2019 00:53:39 +0000 (0:00:01.689) 0:16:39.245 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Monday 07 January 2019 00:53:41 +0000 (0:00:01.884) 0:16:41.130 ********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (49 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Monday 07 January 2019 00:54:05 +0000 (0:00:23.308) 0:17:04.439 ********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Monday 07 January 2019 00:54:06 +0000 (0:00:01.739) 0:17:06.178 ********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Monday 07 January 2019 00:54:08 +0000 (0:00:01.446) 0:17:07.624 ********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Monday 07 January 2019 00:54:09 +0000 (0:00:01.537) 0:17:09.162 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Monday 07 January 2019 00:54:11 +0000 (0:00:01.668) 0:17:10.831 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Monday 07 January 2019 00:54:13 +0000 (0:00:01.765) 0:17:12.597 ********
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Monday 07 January 2019 00:54:14 +0000 (0:00:01.297) 0:17:13.895 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Monday 07 January 2019 00:54:14 +0000 (0:00:00.344) 0:17:14.239 ********
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).
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2 services] *********************************
Monday 07 January 2019 00:55:50 +0000 (0:01:35.455) 0:18:49.695 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Monday 07 January 2019 00:55:52 +0000 (0:00:01.941) 0:18:51.637 ********
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 07 January 2019 00:55:52 +0000 (0:00:00.212) 0:18:51.849 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Monday 07 January 2019 00:55:52 +0000 (0:00:00.368) 0:18:52.217 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 07 January 2019 00:55:54 +0000 (0:00:01.667) 0:18:53.885 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Monday 07 January 2019 00:55:54 +0000 (0:00:00.298) 0:18:54.184 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Monday 07 January 2019 00:55:56 +0000 (0:00:01.591) 0:18:55.775 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Monday 07 January 2019 00:55:56 +0000 (0:00:00.352) 0:18:56.128 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Monday 07 January 2019 00:55:58 +0000 (0:00:01.813) 0:18:57.941 ********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Monday 07 January 2019 00:56:00 +0000 (0:00:01.676) 0:18:59.617 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Monday 07 January 2019 00:56:00 +0000 (0:00:00.352) 0:18:59.970 ********
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.26.163:24007/v1/peers"}
to retry, use: --limit @/root/gcs/deploy/vagrant-playbook.retry
PLAY RECAP *********************************************************************
kube1 : ok=383 changed=113 unreachable=0 failed=1
kube2 : ok=293 changed=91 unreachable=0 failed=0
kube3 : ok=254 changed=71 unreachable=0 failed=0
Monday 07 January 2019 01:05:38 +0000 (0:09:37.863) 0:28:37.833 ********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 577.86s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 95.46s
kubernetes/master : Master | wait for the apiserver to be running ------ 43.71s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.62s
Wait for host to be available ------------------------------------------ 32.09s
Install packages ------------------------------------------------------- 31.36s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 29.75s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 26.17s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 23.31s
kubernetes/master : Master | wait for kube-controller-manager ---------- 19.16s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 18.18s
download : file_download | Download item ------------------------------- 13.48s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 13.02s
gather facts from all instances ---------------------------------------- 12.54s
etcd : reload etcd ----------------------------------------------------- 11.69s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 11.38s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 10.89s
docker : Docker | pause while Docker restarts -------------------------- 10.42s
download : container_download | Download containers if pull is required or told to always pull (all nodes) --- 9.37s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests --- 9.35s
==> 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