[CI-results] Build failed in Jenkins: gluster_anteater_gcs #39
ci at centos.org
ci at centos.org
Sat Jan 5 01:16:39 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/39/display/redirect>
------------------------------------------
[...truncated 576.53 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-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] ******************************
Saturday 05 January 2019 01:04:39 +0000 (0:00:26.476) 0:16:21.586 ******
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 05 January 2019 01:04:39 +0000 (0:00:00.269) 0:16:21.855 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Saturday 05 January 2019 01:04:40 +0000 (0:00:00.556) 0:16:22.412 ******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Saturday 05 January 2019 01:04:42 +0000 (0:00:02.122) 0:16:24.535 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Saturday 05 January 2019 01:04:42 +0000 (0:00:00.435) 0:16:24.971 ******
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Saturday 05 January 2019 01:04:44 +0000 (0:00:01.944) 0:16:26.915 ******
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Saturday 05 January 2019 01:04:45 +0000 (0:00:00.408) 0:16:27.324 ******
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Saturday 05 January 2019 01:04:46 +0000 (0:00:01.946) 0:16:29.271 ******
ok: [kube1]
TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Saturday 05 January 2019 01:04:48 +0000 (0:00:01.699) 0:16:30.971 ******
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Saturday 05 January 2019 01:04:50 +0000 (0:00:01.602) 0:16:32.573 ******
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Saturday 05 January 2019 01:04:51 +0000 (0:00:01.629) 0:16:34.203 ******
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Saturday 05 January 2019 01:05:04 +0000 (0:00:12.259) 0:16:46.462 ******
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Saturday 05 January 2019 01:05:05 +0000 (0:00:01.806) 0:16:48.269 ******
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Saturday 05 January 2019 01:05:07 +0000 (0:00:01.364) 0:16:49.634 ******
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Saturday 05 January 2019 01:05:08 +0000 (0:00:01.371) 0:16:51.005 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Saturday 05 January 2019 01:05:10 +0000 (0:00:01.768) 0:16:52.773 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Saturday 05 January 2019 01:05:12 +0000 (0:00:01.811) 0:16:54.584 ******
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Saturday 05 January 2019 01:05:13 +0000 (0:00:01.305) 0:16:55.890 ******
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Saturday 05 January 2019 01:05:13 +0000 (0:00:00.318) 0:16:56.209 ******
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] *********************************
Saturday 05 January 2019 01:06:49 +0000 (0:01:35.366) 0:18:31.575 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Saturday 05 January 2019 01:06:50 +0000 (0:00:01.530) 0:18:33.106 ******
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 05 January 2019 01:06:51 +0000 (0:00:00.187) 0:18:33.294 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Saturday 05 January 2019 01:06:51 +0000 (0:00:00.362) 0:18:33.656 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 05 January 2019 01:06:53 +0000 (0:00:01.632) 0:18:35.289 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Saturday 05 January 2019 01:06:53 +0000 (0:00:00.330) 0:18:35.620 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Saturday 05 January 2019 01:06:54 +0000 (0:00:01.621) 0:18:37.242 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Saturday 05 January 2019 01:06:55 +0000 (0:00:00.332) 0:18:37.575 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Saturday 05 January 2019 01:06:58 +0000 (0:00:02.871) 0:18:40.446 ******
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Saturday 05 January 2019 01:06:59 +0000 (0:00:01.487) 0:18:41.934 ******
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Saturday 05 January 2019 01:06:59 +0000 (0:00:00.295) 0:18:42.229 ******
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.36.37: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
Saturday 05 January 2019 01:16:36 +0000 (0:09:36.509) 0:28:18.739 ******
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 576.51s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 95.37s
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) -- 33.58s
etcd : Gen_certs | Write etcd master certs ----------------------------- 32.46s
Install packages ------------------------------------------------------- 31.49s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 26.48s
Wait for host to be available ------------------------------------------ 20.95s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 19.41s
kubernetes/master : Master | wait for kube-controller-manager ---------- 14.73s
gather facts from all instances ---------------------------------------- 14.19s
etcd : Gen_certs | Gather etcd master certs ---------------------------- 12.73s
download : file_download | Download item ------------------------------- 12.46s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 12.26s
etcd : reload etcd ----------------------------------------------------- 11.80s
kubernetes-apps/ansible : Kubernetes Apps | Lay Down CoreDNS Template -- 11.11s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Apply manifests -- 10.61s
kubernetes-apps/external_provisioner/local_volume_provisioner : Local Volume Provisioner | Create manifests -- 10.53s
docker : Docker | pause while Docker restarts -------------------------- 10.39s
etcd : wait for etcd up ------------------------------------------------- 9.82s
==> 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