[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 506 - Fixed!
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/506/ Build Number: 506 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #504 [Sahina Bose] hc-suite: Changes as per gluster-ansible update [Sandro Bonazzola] ovirt-wgt: switch from 4.2 to 4.3 Changes for Build #505 [jenkins CI] Auto create ovirt-4.1-stable [Sandro Bonazzola] vdsm-jsonrpc-java: add 4.3 jobs [Ehud Yonasi] conftest.py: Added branch and tag functionality. Changes for Build #506 [Galit Rosenthal] Change the version of centos newer - Failed Tests: - All tests passed___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/B6XPL6HAKT4R5WEL3DYOTYN2W55MGEG3/
[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 506 - Fixed!
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/506/ Build Number: 506 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success: - Changes for Build #505 [jenkins CI] Auto create ovirt-4.1-stable [Sandro Bonazzola] vdsm-jsonrpc-java: add 4.3 jobs [Ehud Yonasi] conftest.py: Added branch and tag functionality. Changes for Build #506 [Galit Rosenthal] Change the version of centos newer - Failed Tests: - All tests passed___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CG7AE7O3ZZIYWWVYAACOKFIOFNM5XKUR/
oVirt infra daily report - unstable production jobs - 757
Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/757//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins RHEVM CI Jenkins Daily Report - 07/03/2019 00 Unstable Critical ovirt-engine-api-model_master_build-artifacts-fc28-x86_64 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-master_change-queue-tester This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_compat-4.1-suite-master This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_compat-4.2-suite-master This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_hc-basic-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_hc-basic-suite-master This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-ansible-suite-4.3 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-ipv6-suite-master This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_he-basic-iscsi-suite-master This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_master_standard-poll-upstream-sources This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_network-suite-4.3 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo. ovirt-system-tests_openshift-on-ovirt-suite-4.2 This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the jenkins repo.
[CQ]: 98191, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
A system test invoked by the "ovirt-master" change queue including change 98191,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 97381,22 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97381,22 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98191/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97381/22 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13317/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/XK4ISN7DIYTGQIDU7FGYUKNF2VENLA5J/
Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine-nodejs-modules) ] [ 27-02-2019 ] [ 002_bootstrap.add_vm2_lease ]
On Thu, Mar 7, 2019 at 8:50 PM Dafna Ron wrote:
> I report this issue to the list and the test owner is more then welcome to
> respond.
> Galit, can you please review the skiptest
> https://gerrit.ovirt.org/#/c/98191/
>
I looked at engine and vdsm logs, and I don't think the add_vm2_lease test
is related
so there is no point to disable it.
It seems that just after finishing resize_and_refresh_storage_domain test:
2019-02-27 13:37:21,036-0500 INFO (jsonrpc/5) [vdsm.api] START
resizePV(sdUUID=u'34311cc1-c4d2-4cfe-88b5-dd5ad72261d3',
spUUID=u'717575a9-7818-460d-ba3a-d5bdd8ef9ed3',
guid=u'360014054e5952dc174c4a12b971ea45c', options=None)
from=:::192.168.201.4,43920,
flow_id=f204cfe2-ef48-429d-ab33-e1175d0530a0,
task_id=5908a867-5e11-474f-8119-49cfe219d4c8 (api:48)
2019-02-27 13:37:21,499-0500 INFO (jsonrpc/5) [vdsm.api] FINISH resizePV
return={'size': '24293408768'} from=:::192.168.201.4,43920,
flow_id=f204cfe2-ef48-429d-ab33-e1175d0530a0,
task_id=5908a867-5e11-474f-8119-49cfe219d4c8 (api:54)
Engine try to lookup the vm lease. The lookup fails (expected since there
is no such lease):
2019-02-27 13:37:21,968-0500 INFO (jsonrpc/1) [vdsm.api] START
lease_info(lease={u'sd_id': u'b370b91d-00b5-4f62-9270-ac0acd47d075',
u'lease_id': u'3500eb82-e5e2-4e24-b41c-ea02d9f6adee'})
from=:::192.168.201.4,43920,
flow_id=117dec74-ad59-4b12-8148-b2c130337c10,
task_id=9c297d41-0aa7-4c74-b268-b710e666bc6c (api:48)
2019-02-27 13:37:21,987-0500 INFO (jsonrpc/1) [vdsm.api] FINISH lease_info
error=No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee
from=:::192.168.201.4,43920,
flow_id=117dec74-ad59-4b12-8148-b2c130337c10,
task_id=9c297d41-0aa7-4c74-b268-b710e666bc6c (api:52)
On engine side, we see immediately after that:
2019-02-27 13:37:22,078-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-1) [117dec74-ad59-4b12-8148-b2c130337c10] method:
getListForSpmSelection, params: [717575a9-7818-460d-ba3a-d5bdd8ef9ed3],
timeElapsed: 12ms
Which means nothing to me, but it seems that engine treat the expected
error to lookup the lease
as fatal error in the spm.
Soon engine try to stop the spm on host-0, which make no sense:
2019-02-27 13:37:22,125-05 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.SpmStopVDSCommand] (default
task-1) [117dec74-ad59-4b12-8148-b2c130337c10] SpmStopVDSCommand::Stopping
SPM on vds 'lago-basic-suite-master-host-0', pool id
'717575a9-7818-460d-ba3a-d5bdd8ef9ed3'
At the same time, host1 has trouble to see the LUNs, and fail to connect to
the pool:
2019-02-27 13:37:20,014-0500 INFO (jsonrpc/4) [vdsm.api] START
getDeviceList(storageType=3, guids=[u'360014055ad799e3a968444abdaefa323',
u'360014054e5952dc174c4a12b971ea45c'], checkStatus=False, options={})
from=:::192.168.201.4,33922,
flow_id=f204cfe2-ef48-429d-ab33-e1175d0530a0,
task_id=78fb7d20-8bec-4561-9867-da4174d181a6 (api:48)
2019-02-27 13:37:20,340-0500 INFO (jsonrpc/4) [vdsm.api] FINISH
getDeviceList return={'devList': []} from=:::192.168.201.4,33922,
flow_id=f204cfe2-ef48-429d-ab33-e1175d
0530a0, task_id=78fb7d20-8bec-4561-9867-da4174d181a6 (api:54)
The host does not see any LUNs.
So of course it cannot see master storage domain.
2019-02-27 13:37:22,718-0500 INFO (jsonrpc/6) [vdsm.api] FINISH
connectStoragePool error=Cannot find master domain:
u'spUUID=717575a9-7818-460d-ba3a-d5bdd8ef9ed3, msdUUID=3
So we probably go into SPM recovery flow which take some time, and adding
lease is just a victim of that,
since adding leases requires SPM.
We need to answer these questions:
- why host 1 does not see storage? we have seen this many time in the past
- why engine try to stop the spm on a host 0 that has no issue?
(maybe related to incorrect handling of "no such lease" error?)
- why the previous tests did not detect that host 1 was not connected to
storage?
- why the previous test did not wait until both hosts are connected to
storage?
We can try to increase the timeout of the add lease test, so we can recover
if the SPM is lost
for some reason during this test, but this only hides the real storage
issues.
Since this is not reproducible, and we don't understand the storage
failures, we should run OST
again after failures, and keep failing logs so we can investigate them
later.
Strangely, we don't experience this issue on master - I did 20-30 OST runs
in the last 2 weeks,
and the only issue I have seen is random host_devices failure. Why the
change queue has
move failures? What is the difference between OST master runs and the
change queue?
Nir
>
> Thanks,
> Dafna
>
>
> On Tue, Mar 5, 2019 at 2:43 PM Nir Soffer wrote:
>
>>
>>
>> On Tue, Mar 5, 2019, 13:27 Eyal Shenitzky >
>>>
>>>
>>> On Tue, Mar 5, 2019 at 12:58 PM Dafna Ron wrote:
>>>
Tal,
I see the bug is in post but the patch was not merged yet:
https://gerrit.ovirt.org/#/c/98191/
can you tell me when will we merge the patch? as I rather not add
SkipTest if this will be merged soon,
error failed to execute stage 'misc configuration': failed to start service 'openvswitch'
I'm starting in the world of ovirt, so I would appreciate the help I'm trying to install ovirt-engine and it gives me the following error error failed to execute stage 'misc configuration': failed to start service 'openvswitch' Could someone guide me to find the solution? ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CTIAQUY2ZXFPIZSD3YV6OISQ3BQ77NKB/
[CQ]: 97381,22 (vdsm) failed "ovirt-master" system tests
Change 97381,22 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" 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/97381/22 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13314/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FN4SCMBKYGSY32M3G2R3LLUYJHKM6RVR/
[CQ]: 10a3041 (ovirt-ansible-shutdown-env) failed "ovirt-4.3" system tests
Change 10a3041 (ovirt-ansible-shutdown-env) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-shutdown-env/commit/10a3041ed983320920b7a0f74e0de303faf403d0 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/156/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EK2UCHOFLYPBGZXAEIUR4JZBUL5W6ODL/
Re: [ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine-nodejs-modules) ] [ 27-02-2019 ] [ 002_bootstrap.add_vm2_lease ]
I report this issue to the list and the test owner is more then welcome to
respond.
Galit, can you please review the skiptest
https://gerrit.ovirt.org/#/c/98191/
Thanks,
Dafna
On Tue, Mar 5, 2019 at 2:43 PM Nir Soffer wrote:
>
>
> On Tue, Mar 5, 2019, 13:27 Eyal Shenitzky
>>
>>
>> On Tue, Mar 5, 2019 at 12:58 PM Dafna Ron wrote:
>>
>>> Tal,
>>>
>>> I see the bug is in post but the patch was not merged yet:
>>> https://gerrit.ovirt.org/#/c/98191/
>>>
>>> can you tell me when will we merge the patch? as I rather not add
>>> SkipTest if this will be merged soon,
>>>
>>> thanks,
>>> Dafna
>>>
>>>
>>> On Mon, Mar 4, 2019 at 10:42 AM Dafna Ron wrote:
>>>
As I had another failure of this today I will be disabling this test
until issue is resolved (https://bugzilla.redhat.com/1684267)
Thanks,
Dafna
On Thu, Feb 28, 2019 at 8:48 PM Nir Soffer wrote:
> On Thu, Feb 28, 2019 at 11:52 AM Dafna Ron wrote:
>
>> Hi,
>>
>> We have a failure on the project in basic suite, master branch. The
>> recent failure was in patch:
>> https://gerrit.ovirt.org/#/c/98087/1 - Add pre-seed for ovirt-web-ui
>>
>> CQ is pointing at the below as the root cause (which was merged a
>> while back):
>> https://gerrit.ovirt.org/#/c/97491/ - Add pre-seed for ovirt-web-ui
>>
>> Can you please check the issue as it seems both patches are changing
>> the same thing and the project seem to be broken since
>> https://gerrit.ovirt.org/#/c/97491/3
>>
>> Latest failure:
>> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/
>>
>> Logs:
>>
>> https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13171/artifact/basic-suite.el7.x86_64/test_logs/basic-suite-master/post-002_bootstrap.py/
>>
>> errors from logs:
>> Engine:
>>
>> 2019-02-27 13:37:28,479-05 ERROR
>> [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [74283e25]
>> Transaction rolled-back for command
>> 'org.ovirt.engine.core.bll.UpdateVmCommand'.
>> 2019-02-27 13:37:28,483-05 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-1) [74283e25] EVENT_ID: USER_FAILED_UPDATE_VM(58), Failed
>> to
>> update VM vm2 (User: admin@inter
>> nal-authz).
>> 2019-02-27 13:37:28,485-05 INFO
>> [org.ovirt.engine.core.bll.UpdateVmCommand] (default task-1) [74283e25]
>> Lock freed to object 'EngineLock:{exclusiveLocks='[vm2=VM_NAME]',
>> sharedLocks='[3500eb82-e5e2-4e24-b41c-ea
>> 02d9f6adee=VM]'}'
>> 2019-02-27 13:37:28,485-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-1) [74283e25] method: runAction, params: [UpdateVm,
>> VmManagementParametersBase:{commandId='340
>> 59769-05b9-429e-8356-f6b9b9953f55', user='admin',
>> commandType='UpdateVm', vmId='3500eb82-e5e2-4e24-b41c-ea02d9f6adee'}],
>> timeElapsed: 6618ms
>> 2019-02-27 13:37:28,486-05 ERROR
>> [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default
>> task-1) [] Operation Failed: []
>> 2019-02-27 13:37:28,579-05 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-85) [] method: get,
>> params:
>> [e29c0ba1-464c-4eb4-a8f2-c6933d9
>> 9969a], timeElapsed: 3ms
>>
>>
>> vdsm:
>>
>> 2019-02-27 13:37:21,987-0500 INFO (jsonrpc/1) [vdsm.api] FINISH
>> lease_info error=No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee
>> from=:::192.168.201.4,43920,
>> flow_id=117dec74-ad59-4b12-8148-b2c130337c10,
>> task_id=9c297d41-0aa7-4c74-b268-b710e666bc6c (api:52)
>> 2019-02-27 13:37:21,988-0500 ERROR (jsonrpc/1)
>> [storage.TaskManager.Task] (Task='9c297d41-0aa7-4c74-b268-b710e666bc6c')
>> Unexpected error (task:875)
>> Traceback (most recent call last):
>> File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line
>> 882, in _run
>> return fn(*args, **kargs)
>> File "", line 2, in lease_info
>> File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line
>> 50, in method
>> ret = func(*args, **kwargs)
>> File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line
>> 3702, in lease_info
>> info = dom.lease_info(lease.lease_id)
>> File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line
>> 674, in lease_info
>> return vol.lookup(lease_id)
>> File "/usr/lib/python2.7/site-packages/vdsm/storage/xlease.py",
>> line 553, in lookup
>> raise NoSuchLease(lease_id)
>> NoSuchLease: No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee
>>
>
> This is not an error of vdsm. Someone asked for information about a
> non-existing lease,
> and vdsm fail the request with the expected error:
[CQ]: 95460, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
A system test invoked by the "ovirt-master" change queue including change 95460,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97965,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97965,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/95460/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97965/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13310/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PXTRCHIQIM25E4T2VMHS3IMZ6WBKMHW5/
[CQ]: 98351, 1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests, but isn't the failure root cause
A system test invoked by the "ovirt-4.3" change queue including change 98351,1 (vdsm-jsonrpc-java) failed. However, this change seems not to be the root cause for this failure. Change 94713,1 (vdsm-jsonrpc-java) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 94713,1 (vdsm-jsonrpc-java) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98351/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/94713/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/153/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/M72LOMGZA7UGOOGRDVX46I3L7F2GZ7CA/
[CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
A system test invoked by the "ovirt-master" change queue including change 98221,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97965,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97965,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98221/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97965/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7VK6YB7KCKZRYRL63GMQK2CMNH7EM2DL/
[CQ]: 10a3041 (ovirt-ansible-shutdown-env) failed "ovirt-4.3" system tests
Change 10a3041 (ovirt-ansible-shutdown-env) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-shutdown-env/commit/10a3041ed983320920b7a0f74e0de303faf403d0 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/151/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/EEAI4R7PCALAV267J6LKOK4GD5SHLGHZ/
[CQ]: 98276, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
A system test invoked by the "ovirt-master" change queue including change 98276,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97965,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97965,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/98276/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97965/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13302/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5CKV5TTL3EAAONUWLOY26FCR6BKCZU56/
[CQ]: 10a3041 (ovirt-ansible-shutdown-env) failed "ovirt-4.3" system tests
Change 10a3041 (ovirt-ansible-shutdown-env) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-shutdown-env/commit/10a3041ed983320920b7a0f74e0de303faf403d0 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/147/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BWSURJL7F3UPOU6JOMHXEPJ4DW3C2PKG/
[CQ]: 94713,1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests
Change 94713,1 (vdsm-jsonrpc-java) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/94713/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/145/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FKP24S3X23XNNSLHMKPZ2ZU6JHIVBVAZ/
[CQ]: 94713,1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests
Change 94713,1 (vdsm-jsonrpc-java) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/94713/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/142/ ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/J5ZIFNEF2ZHKMPMJFJJANJV3QJ3SNWRI/
[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39140#comment-39140 ] Liora Milbaum commented on OVIRT-2001: -- [~bkor...@redhat.com] sure. will do. > Create FAQ/Knowledge Base/HOWTO pages for STDCI > --- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation >Reporter: Barak Korren >Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from > case/task-specific documentation. So we should have a FAQ page or a Knowledge > Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues > and solutions, so we will use comments on this ticket to collect them as they > arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/E3EZ6YQILR3ENB7WQUTH5GLBZFSYJ35O/
[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liora Milbaum reassigned OVIRT-2001: Assignee: Liora Milbaum (was: infra) > Create FAQ/Knowledge Base/HOWTO pages for STDCI > --- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation >Reporter: Barak Korren >Assignee: Liora Milbaum > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from > case/task-specific documentation. So we should have a FAQ page or a Knowledge > Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues > and solutions, so we will use comments on this ticket to collect them as they > arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/GPPPBNKSBQCXZH4BCAZXB5OUG24GZHP4/
[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base/HOWTO pages for STDCI
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39136#comment-39136 ] Barak Korren commented on OVIRT-2001: - [~lmilb...@redhat.com] if we reached consensus about managing a KB in the google doc you've created, can you take the information that we collected in the comments here and put it there? > Create FAQ/Knowledge Base/HOWTO pages for STDCI > --- > > Key: OVIRT-2001 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Documentation >Reporter: Barak Korren >Assignee: infra > Labels: first_time_task > > There are many common use cases and issues in STDCI that could benefit from > case/task-specific documentation. So we should have a FAQ page or a Knowledge > Base about STDCI to cover these issues. > Before we can make the page we need a critical mass (at least 3) of issues > and solutions, so we will use comments on this ticket to collect them as they > arise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/RYHIXT36F4SZ4R7Y56Z2HMGD3PBLOE4Q/
