1:07 p.m.
Change 89634,2 (ovirt-imageio) is probably the reason behind recent system test
failures in the "ovirt-4.2" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/89634/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1502/
1:36 p.m.
On 1 April 2018 at 13:07, oVirt Jenkins <jenkins(a)ovirt.org> wrote:
Change 89634,2 (ovirt-imageio) is probably the reason behind recent
system test
failures in the "ovirt-4.2" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/89634/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1502/
Looks like a real issue, report sent to devel.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
3:02 p.m.
On Sun, Apr 1, 2018 at 1:08 PM oVirt Jenkins <jenkins(a)ovirt.org> wrote:
Change 89634,2 (ovirt-imageio) is probably the reason behind recent
system
test
failures in the "ovirt-4.2" change queue and needs to be fixed.
This change had been removed from the testing queue. Artifacts build from
this
change will not be released until it is fixed.
The change is not related to the error, please add the change to the
testing queue.
The change fix the response of ovirt-imageio-daemon for OPTIONS request.
This request is not sent while attaching a storage domain.
If you run the test again, you will probably see that it is a flaky test.
Nir
For further details about the change see:
https://gerrit.ovirt.org/#/c/89634/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1502/
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
3:08 p.m.
On Sun, Apr 1, 2018 at 3:03 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
On Sun, Apr 1, 2018 at 1:08 PM oVirt Jenkins
<jenkins(a)ovirt.org> wrote:
> Change 89634,2 (ovirt-imageio) is probably the reason behind recent
> system test
> failures in the "ovirt-4.2" change queue and needs to be fixed.
>
> This change had been removed from the testing queue. Artifacts build from
> this
> change will not be released until it is fixed.
>
The change is not related to the error, please add the change to the
testing queue.
Indeed. According to the log[*], the failure occurs during attach storage
domain procedure, which is not related to imageio.
By the error, it seems that vdsm wasn't responding/accessible in the test
env?
[*]
File
"/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/007_sd_reattach.py",
line 83, in reattach_storage_domain
dc.storage_domains_service().add(sd)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
line 2944, in add
return self._internal_add(storage_domain, headers, query, wait)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
232, in _internal_add
return future.wait() if wait else future
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
55, in wait
return self._code(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
229, in callback
self._check_fault(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
132, in _check_fault
self._raise_error(response, body)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
118, in _raise_error
raise error
Error: Fault reason is "Operation Failed". Fault detail is "[Network
error during communication with the Host.]". HTTP response code is
400.
The change fix the response of ovirt-imageio-daemon for OPTIONS request.
This request is not sent while attaching a storage domain.
If you run the test again, you will probably see that it is a flaky test.
Nir
>
> For further details about the change see:
> https://gerrit.ovirt.org/#/c/89634/2
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1502/
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
3:12 p.m.
On 1 April 2018 at 15:08, Daniel Erez <derez(a)redhat.com> wrote:
On Sun, Apr 1, 2018 at 3:03 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
>
> On Sun, Apr 1, 2018 at 1:08 PM oVirt Jenkins <jenkins(a)ovirt.org> wrote:
>>
>> Change 89634,2 (ovirt-imageio) is probably the reason behind recent
>> system test
>> failures in the "ovirt-4.2" change queue and needs to be fixed.
>>
>> This change had been removed from the testing queue. Artifacts build from
>> this
>> change will not be released until it is fixed.
>
>
> The change is not related to the error, please add the change to the
> testing queue.
Indeed. According to the log[*], the failure occurs during attach storage
domain procedure, which is not related to imageio.
By the error, it seems that vdsm wasn't responding/accessible in the test
env?
Resubmitted the patch into the CQ.
Who could spend the time to ensure the test is more reliable?
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
3:15 p.m.
On Sun, Apr 1, 2018 at 3:12 PM Barak Korren <bkorren(a)redhat.com> wrote:
On 1 April 2018 at 15:08, Daniel Erez <derez(a)redhat.com>
wrote:
>
>
> On Sun, Apr 1, 2018 at 3:03 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
>>
>> On Sun, Apr 1, 2018 at 1:08 PM oVirt Jenkins <jenkins(a)ovirt.org> wrote:
>>>
>>> Change 89634,2 (ovirt-imageio) is probably the reason behind recent
>>> system test
>>> failures in the "ovirt-4.2" change queue and needs to be fixed.
>>>
>>> This change had been removed from the testing queue. Artifacts build
from
>>> this
>>> change will not be released until it is fixed.
>>
>>
>> The change is not related to the error, please add the change to the
>> testing queue.
>
>
> Indeed. According to the log[*], the failure occurs during attach storage
> domain procedure, which is not related to imageio.
> By the error, it seems that vdsm wasn't responding/accessible in the test
> env?
>
Resubmitted the patch into the CQ.
Who could spend the time to ensure the test is more reliable?
The owner of test.
Do we have some stats about this test? does it fail a lot?
I would open a bug for this.
Nir
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
2427
days inactive
2427
days old
5 comments
4 participants
participants (4)
-
Barak Korren -
Daniel Erez -
Nir Soffer -
oVirt Jenkins