[JIRA] (OVIRT-1607) Failed ovirt-system-tests_master_check-patch-el7-x86_64

[Evgheni Dereveanchin (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34785#comment-34785 ] 

Evgheni Dereveanchin commented on OVIRT-1607:
---------------------------------------------

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

Wget was able to access the proxy and the proxy tried to fetch the URL but got a 404 error from jenkins:

1503475892.751      4 66.187.230.21 TCP_MISS/404 878 GET http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/ - HIER_DIRECT/66.187.230.92 text/html

I get a 404 error when accessing this URL as well so there's some error in the fetching script:
http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64//artifact/exported-artifacts/

[~ngoldin at 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:

1503475797.567   9880 66.187.230.21 TCP_REFRESH_UNMODIFIED/200 822060496 GET 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 - HIER_DIRECT/66.187.230.92 application/octet-stream

This one has both a build number and file name and should be added here.

> Failed ovirt-system-tests_master_check-patch-el7-x86_64
> -------------------------------------------------------
>
>                 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
>
> 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] https://gerrit.ovirt.org/80820
> [2] https://gerrit.ovirt.org/79345
> [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/1467/
> -- 
> Didi



--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100059)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20170824/d24e2e5d/attachment.html>