<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34785#comment-34785 ]</pre>
<h3>Evgheni Dereveanchin commented on OVIRT-1607:</h3>
<p>Interesting, in this particular case it doesn't look like a DNS issue. The connection was as follows: wget -> proxy01.phx.ovirt.org -> jenkins.ovirt.org</p>
<p>Wget was able to access the proxy and the proxy tried to fetch the URL but got a 404 error from jenkins:</p>
<p>1503475892.751 4 66.187.230.21 TCP_MISS/404 878 GET <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/">http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/</a> – HIER_DIRECT/66.187.230.92 text/html</p>
<p>I get a 404 error when accessing this URL as well so there's some error in the fetching script: <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/">http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/</a></p>
<p>[~ngoldin@redhat.com] why are we not appending the artifact name or build number to the URL above? In squid logs I see a successful fetch of the Appliance via the proxy with a correct URL:</p>
<p>1503475797.567 9880 66.187.230.21 TCP_REFRESH_UNMODIFIED/200 822060496 GET <a href="http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/524/artifact/exported-artifacts/oVirt-Engine-Appliance-CentOS-x86_64-7-20170822.ova">http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/524/artifact/exported-artifacts/oVirt-Engine-Appliance-CentOS-x86_64-7-20170822.ova</a> – HIER_DIRECT/66.187.230.92 application/octet-stream</p>
<p>This one has both a build number and file name and should be added here.</p>
<blockquote><h3>Failed ovirt-system-tests_master_check-patch-el7-x86_64</h3>
<pre> Key: OVIRT-1607
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1607
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>I want to verify [1]. It (expectedly) failed in the past, needed [2]. [2] was merged yesterday and [1] still fails. I retriggered it several times, and it failed due to different reasons. Last was [3]: 08:11:38 + find /dev/shm/ost/deployment-image-ng-suite-master -type f ‘(’ -iname ‘nose*.xml’ -o -iname ‘*.junit.xml’ ‘)’ -exec mv ‘{}’ exported-artifacts/ ‘;’ 08:11:38 find: ���/dev/shm/ost/deployment-image-ng-suite-master���: No such file or directory Please have a look. Thanks, [1] <a href="https://gerrit.ovirt.org/80820">https://gerrit.ovirt.org/80820</a> [2] <a href="https://gerrit.ovirt.org/79345">https://gerrit.ovirt.org/79345</a> [3] <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1467/">http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1467/</a> — Didi</p></blockquote>
<p>— This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzYS3r1Q939T2sgz1L1GoZCem-2BYGvNGHDOX5Gk2XiIHy9v060CKZXYqKmpwU8Pkaaw4w6CPeroyHMrmIBvFxT0L6iKUFlLKdeAV7pVf0DTdPQJ15hrqfBqEgDRtdLKZXHVHDUvGRV2Kci2CNEK7jTa6rG3BLLFyLVeViSu4llftukeA-2FKJHjgdXm1f-2F5Ff5inQRJrs4cIKoV21yUw-3D" 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>