<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre>
<h3>Barak Korren updated OVIRT-1870:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>kubevirt_kubevirt_standard-check-pr jobs often get stuck</h3>
<pre> Key: OVIRT-1870
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1870
Project: oVirt - virtualization made easy
Issue Type: Bug
Components: CI client projects, Standard CI (Pipelines)
Reporter: Evgheni Dereveanchin
Assignee: infra</pre>
<p>kubevirt_kubevirt_standard-check-pr jobs often get stuck waiting forever for a connection to get established: <a href="http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/376/console">http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/376/console</a> <a href="http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/377/console">http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/377/console</a> <a href="http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/378/console">http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/378/console</a> <a href="http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/380/console">http://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/380/console</a> The following message keeps repeating all the time: 17:03:32 [check-patch.el7.x86_64] ++ awk ‘/virt-controller/ && /true/’ 17:03:32 [check-patch.el7.x86_64] ++ kubectl get pods -n kube-system ‘-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name’ --no-headers 17:03:32 [check-patch.el7.x86_64] ++ wc -l 17:03:32 [check-patch.el7.x86_64] ++ cluster/kubectl.sh get pods -n kube-system ‘-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name’ --no-headers 17:03:44 [check-patch.el7.x86_64] Unable to connect to the server: dial tcp 192.168.121.111:6443: getsockopt: no route to host 17:03:44 [check-patch.el7.x86_64] + ‘[’ 0 -lt 1 ‘]’ 17:03:44 [check-patch.el7.x86_64] + echo ‘Waiting for KubeVirt virt-controller container to become ready …’ 17:03:44 [check-patch.el7.x86_64] Waiting for KubeVirt virt-controller container to become ready … 17:03:44 [check-patch.el7.x86_64] + kubectl get pods -n kube-system ‘-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name’ --no-headers 17:03:44 [check-patch.el7.x86_64] + awk ‘/virt-controller/ && /true/’ 17:03:44 [check-patch.el7.x86_64] + cluster/kubectl.sh get pods -n kube-system ‘-ocustom-columns=status:status.containerStatuses[*].ready,metadata:metadata.name’ --no-headers 17:03:44 [check-patch.el7.x86_64] + wc -l 17:03:56 [check-patch.el7.x86_64] Unable to connect to the server: dial tcp 192.168.121.111:6443: getsockopt: no route to host 17:03:56 [check-patch.el7.x86_64] 0 17:03:56 [check-patch.el7.x86_64] + sleep 10 Need to implement timeouts as this takes up bare metal systems for days and weeks until someone manually kills the job</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3tuiUfRTk64K-2BOjGpF-2BuMzoJRRB1ifzZIErtIxTccLy521zz7OxZViB5mnpbbwYJFz6flgevXOzUJVH-2FqBqvcqqqKIp3p4OcyDFOsRwvaLk1r7X8JpLEbbYtQ-2F8se-2FAoG3NqMy6MEF960fM4WCfArIPipDAxV3I9QtDxwIZkeNWD9yApPsdJra3V4NT7hIOoTif46hN9A2Na-2BIseHngSSOzrSPo87Xs5dlTOp5AnrSacdMEjvtn-2Fb-2B7b-2F25UMdFrrmosGXMR8JFQqmPiWg64dwfONOmrRlpM-2FL4VMK0iQf-2BS-2BMgYtwsFHBcqrPJCznYQh0pvmRBSidfXuLr302-2FBk6OYNUsuIn5NiHRGiIxURWbbxjfkKc-2BN3fPZBJIB9F-2FEtddhFaoVjNECBzestyRyOCtdrY7prk62nlN8U" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>