Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Failed ovirt-system-tests_master_check-patch-el7-x86_64

Description

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

Activity

Show:

Eyal Edri August 29, 2017 at 1:53 PM

please reopen if it happens again.

Former user August 29, 2017 at 1:48 PM

+1 good call

Eyal Edri August 29, 2017 at 1:39 PM

there was a DNS outage during that time, so it might be caused by that.
If we can't reproduce it then I think we'll close the ticket and re-open if we see it again.

Former user August 29, 2017 at 1:37 PM

Didn't see it happening anymore, perhaps a glitch in the jenkins api didn't return buildNumber ?

Eyal Edri August 29, 2017 at 1:29 PM

Is this still an issue?

Former user August 24, 2017 at 1:14 PM

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/

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.

Anton Marchukov August 24, 2017 at 12:16 PM

There are some occasional flaky DNS stuff going on. But this job has other problems since DNS is not that flaky.

Cannot Reproduce

Details

Assignee

Reporter

Priority

Created August 23, 2017 at 8:43 AM
Updated August 31, 2017 at 1:02 PM
Resolved August 29, 2017 at 1:53 PM

Flag notifications