[CI-results] Build failed in Jenkins: gluster_anteater_gcs #40
ci at centos.org
ci at centos.org
Sun Jan 6 01:25:50 UTC 2019
See <https://ci.centos.org/job/gluster_anteater_gcs/40/display/redirect>
------------------------------------------
[...truncated 576.58 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-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] ******************************
Sunday 06 January 2019 01:15:18 +0000 (0:00:10.310) 0:09:20.456 ********
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] ***
Sunday 06 January 2019 01:15:18 +0000 (0:00:00.089) 0:09:20.545 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube1 | Create gcs-gd2-kube1.yml] ***
Sunday 06 January 2019 01:15:18 +0000 (0:00:00.137) 0:09:20.683 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Set fact kube_hostname] ***
Sunday 06 January 2019 01:15:19 +0000 (0:00:00.739) 0:09:21.423 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube2 | Create gcs-gd2-kube2.yml] ***
Sunday 06 January 2019 01:15:19 +0000 (0:00:00.152) 0:09:21.576 ********
changed: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Set fact kube_hostname] ***
Sunday 06 January 2019 01:15:20 +0000 (0:00:00.709) 0:09:22.285 ********
ok: [kube1]
TASK [GCS Pre | Manifests | Create GD2 manifests for kube3 | Create gcs-gd2-kube3.yml] ***
Sunday 06 January 2019 01:15:20 +0000 (0:00:00.151) 0:09:22.437 ********
changed: [kube1]
TASK [GCS | Namespace | Create GCS namespace] **********************************
Sunday 06 January 2019 01:15:21 +0000 (0:00:00.748) 0:09:23.185 ********
ok: [kube1]
TASK [GCS | Namespace | Create Monitoring namespace] ***************************
Sunday 06 January 2019 01:15:22 +0000 (0:00:00.648) 0:09:23.834 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Deploy etcd-operator] ******************************
Sunday 06 January 2019 01:15:22 +0000 (0:00:00.648) 0:09:24.482 ********
ok: [kube1]
TASK [GCS | ETCD Operator | Wait for etcd-operator to be available] ************
Sunday 06 January 2019 01:15:23 +0000 (0:00:00.702) 0:09:25.184 ********
FAILED - RETRYING: GCS | ETCD Operator | Wait for etcd-operator to be available (50 retries left).
changed: [kube1]
TASK [GCS | Anthill | Register CRDs] *******************************************
Sunday 06 January 2019 01:15:34 +0000 (0:00:10.934) 0:09:36.119 ********
ok: [kube1]
TASK [Wait for GlusterCluster CRD to be registered] ****************************
Sunday 06 January 2019 01:15:35 +0000 (0:00:00.689) 0:09:36.808 ********
ok: [kube1]
TASK [Wait for GlusterNode CRD to be registered] *******************************
Sunday 06 January 2019 01:15:35 +0000 (0:00:00.531) 0:09:37.340 ********
ok: [kube1]
TASK [GCS | Anthill | Deploy operator] *****************************************
Sunday 06 January 2019 01:15:36 +0000 (0:00:00.501) 0:09:37.841 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Deploy etcd-cluster] ********************************
Sunday 06 January 2019 01:15:36 +0000 (0:00:00.708) 0:09:38.550 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Get etcd-client service] ****************************
Sunday 06 January 2019 01:15:37 +0000 (0:00:00.915) 0:09:39.465 ********
FAILED - RETRYING: GCS | ETCD Cluster | Get etcd-client service (5 retries left).
changed: [kube1]
TASK [GCS | ETCD Cluster | Set etcd_client_endpoint] ***************************
Sunday 06 January 2019 01:15:43 +0000 (0:00:05.955) 0:09:45.420 ********
ok: [kube1]
TASK [GCS | ETCD Cluster | Wait for etcd-cluster to become ready] **************
Sunday 06 January 2019 01:15:43 +0000 (0:00:00.160) 0:09:45.581 ********
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] *********************************
Sunday 06 January 2019 01:16:50 +0000 (0:01:06.179) 0:10:51.761 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy GD2] ******************************************
Sunday 06 January 2019 01:16:50 +0000 (0:00:00.771) 0:10:52.532 ********
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] ******************************
Sunday 06 January 2019 01:16:50 +0000 (0:00:00.090) 0:10:52.623 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube1] ***************************
Sunday 06 January 2019 01:16:51 +0000 (0:00:00.146) 0:10:52.770 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Sunday 06 January 2019 01:16:51 +0000 (0:00:00.762) 0:10:53.533 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube2] ***************************
Sunday 06 January 2019 01:16:51 +0000 (0:00:00.148) 0:10:53.682 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Set fact kube_hostname] ******************************
Sunday 06 January 2019 01:16:52 +0000 (0:00:00.823) 0:10:54.505 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Deploy glusterd2 on kube3] ***************************
Sunday 06 January 2019 01:16:52 +0000 (0:00:00.159) 0:10:54.665 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Get glusterd2-client service] ************************
Sunday 06 January 2019 01:16:53 +0000 (0:00:00.773) 0:10:55.439 ********
changed: [kube1]
TASK [GCS | GD2 Cluster | Set gd2_client_endpoint] *****************************
Sunday 06 January 2019 01:16:54 +0000 (0:00:00.592) 0:10:56.031 ********
ok: [kube1]
TASK [GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready] **********
Sunday 06 January 2019 01:16:54 +0000 (0:00:00.149) 0:10:56.180 ********
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.19.32: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
Sunday 06 January 2019 01:25:50 +0000 (0:08:56.222) 0:19:52.403 ********
===============================================================================
GCS | GD2 Cluster | Wait for glusterd2-cluster to become ready -------- 536.22s
GCS | ETCD Cluster | Wait for etcd-cluster to become ready ------------- 66.18s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 37.77s
kubernetes/master : Master | wait for the apiserver to be running ------ 28.04s
Install packages ------------------------------------------------------- 24.06s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 21.42s
Wait for host to be available ------------------------------------------ 16.50s
Extend root VG --------------------------------------------------------- 15.12s
etcd : Gen_certs | Write etcd master certs ----------------------------- 14.00s
GCS | ETCD Operator | Wait for etcd-operator to be available ----------- 10.93s
etcd : reload etcd ----------------------------------------------------- 10.84s
download : file_download | Download item ------------------------------- 10.60s
download : container_download | Download containers if pull is required or told to always pull (all nodes) -- 10.56s
GCS Pre | Manifests | Sync GCS manifests ------------------------------- 10.31s
docker : Docker | pause while Docker restarts -------------------------- 10.18s
gather facts from all instances ----------------------------------------- 8.11s
etcd : wait for etcd up ------------------------------------------------- 7.93s
kubernetes/master : Master | wait for kube-controller-manager ----------- 7.54s
GCS | ETCD Cluster | Get etcd-client service ---------------------------- 5.96s
kubernetes-apps/network_plugin/flannel : Flannel | Wait for flannel subnet.env file presence --- 5.76s
==> 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