- Infra - oVirt List Archives

[CQ]: 98407, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '19

10 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98407,3 (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/98407/3 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/13352/

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Dafna Ron (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2697: ---------------------------------- we did > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OFT-653) error before starting tests
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OFT-653?page=com.atlassian.jira.plu… ] Liora Milbaum reassigned OFT-653: --------------------------------- Assignee: infra (was: Liora Milbaum) > error before starting tests > --------------------------- > > Key: OFT-653 > URL: https://ovirt-jira.atlassian.net/browse/OFT-653 > Project: OST Failures Tracking > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

3 2

[CQ]: 91993, 39 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '19

10 Mar '19

A system test invoked by the "ovirt-master" change queue including change 91993,39 (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/91993/39 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/13346/

1 0

[JIRA] (OVIRT-2698) Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2698?page=com.atlassian.jira.… ] Liora Milbaum updated OVIRT-2698: --------------------------------- Labels: ost_failures (was: ) > Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to > -------------------------------------------------------------------------------------- > > Key: OVIRT-2698 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2698 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Labels: ost_failures > > [CQ]: 98351, 1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests > https://gerrit.ovirt.org/#/c/94713/1 > http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/153/ > [36m # 001_upgrade_engine.test_initialize_engine: [0m[0m[0m > [36m * Copy /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: [0m[0m[0m > [36m * Copy /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: [32mSuccess[0m (in 0:00:00)[0m > [36m * Collect artifacts: [0m[0m[0m > [36m ~ [Thread-8] Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/default/test_logs/001_upgrade_engine.test_initialize_engine-20190307160642/lago-upgrade-from-prevrelease-suite-4-3-engine/_tmp_otopi*: [31mERROR[0m (in 0:00:00)[0m > [36m - [Thread-8] lago-upgrade-from-prevrelease-suite-4-3-engine: [31mERROR[0m (in 0:00:00)[0m > [36m * Collect artifacts: [31mERROR[0m (in 0:00:01)[0m > [36m # 001_upgrade_engine.test_initialize_engine: [31mERROR[0m (in 0:00:49)[0m > [36m # Results located at /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/001_upgrade_engine.py.junit.xml[0m > [36m@ Run test: 001_upgrade_engine.py: [31mERROR[0m (in 0:00:49)[0m > [31mError occured, aborting > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run > self.cli_plugins[args.ovirtverb].do_run(args) > File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run > self._do_run(**vars(args)) > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper > return func(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper > return func(*args, prefix=prefix, **kwargs) > File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107, in do_ovirt_runtest > raise RuntimeError('Some tests failed') > RuntimeError: Some tests failed[0m -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2698) Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

Liora Milbaum created OVIRT-2698: ------------------------------------ Summary: Upgrade Suite: Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to Key: OVIRT-2698 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2698 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Liora Milbaum Assignee: infra [CQ]: 98351, 1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests https://gerrit.ovirt.org/#/c/94713/1 http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/153/ [36m # 001_upgrade_engine.test_initialize_engine: [0m[0m[0m [36m * Copy /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: [0m[0m[0m [36m * Copy /home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/upgrade-from-prevrelease-suite-4.3/upgrade-engine-answer-file.conf to lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/answer-file-post: [32mSuccess[0m (in 0:00:00)[0m [36m * Collect artifacts: [0m[0m[0m [36m ~ [Thread-8] Copy from lago-upgrade-from-prevrelease-suite-4-3-engine:/tmp/otopi* to /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/default/test_logs/001_upgrade_engine.test_initialize_engine-20190307160642/lago-upgrade-from-prevrelease-suite-4-3-engine/_tmp_otopi*: [31mERROR[0m (in 0:00:00)[0m [36m - [Thread-8] lago-upgrade-from-prevrelease-suite-4-3-engine: [31mERROR[0m (in 0:00:00)[0m [36m * Collect artifacts: [31mERROR[0m (in 0:00:01)[0m [36m # 001_upgrade_engine.test_initialize_engine: [31mERROR[0m (in 0:00:49)[0m [36m # Results located at /dev/shm/ost/deployment-upgrade-from-prevrelease-suite-4.3/001_upgrade_engine.py.junit.xml[0m [36m@ Run test: 001_upgrade_engine.py: [31mERROR[0m (in 0:00:49)[0m [31mError occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107, in do_ovirt_runtest raise RuntimeError('Some tests failed') RuntimeError: Some tests failed[0m -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Liora Milbaum moved OFT-653 to OVIRT-2697: ------------------------------------------ Project: oVirt - virtualization made easy (was: OST Failures Tracking) Workflow: Task Management Workflow (was: Software Simplified Workflow for Project OFT) Key: OVIRT-2697 (was: OFT-653) > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OFT-653) error before starting tests
by Eyal Edri (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OFT-653?page=com.atlassian.jira.plu… ] Eyal Edri commented on OFT-653: ------------------------------- i think we agreed to drop this project IIRC and report issues on the ovirt project, Dafna? On Sun, Mar 10, 2019, 16:47 Liora Milbaum (oVirt JIRA) < > error before starting tests > --------------------------- > > Key: OFT-653 > URL: https://ovirt-jira.atlassian.net/browse/OFT-653 > Project: OST Failures Tracking > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2696) verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status'
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jira.… ] Liora Milbaum updated OVIRT-2696: --------------------------------- Summary: verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status' (was: AttributeError: 'NoneType' object has no attribute 'status') > verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status' > ---------------------------------------------------------------------------------- > > Key: OVIRT-2696 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Priority: High > Labels: ost_failures > > [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > Project name - ovirt-engine > Branch - ovirt-master > Failed Suite - basic suite > Failed test/failed phase > Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ > Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2696) AttributeError: 'NoneType' object has no attribute 'status'
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jira.… ] Liora Milbaum updated OVIRT-2696: --------------------------------- Labels: ost_failures (was: ) > AttributeError: 'NoneType' object has no attribute 'status' > ----------------------------------------------------------- > > Key: OVIRT-2696 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Priority: High > Labels: ost_failures > > [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > Project name - ovirt-engine > Branch - ovirt-master > Failed Suite - basic suite > Failed test/failed phase > Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ > Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2696) AttributeError: 'NoneType' object has no attribute 'status'
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

Liora Milbaum created OVIRT-2696: ------------------------------------ Summary: AttributeError: 'NoneType' object has no attribute 'status' Key: OVIRT-2696 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Liora Milbaum Assignee: infra Priority: High [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause Project name - ovirt-engine Branch - ovirt-master Failed Suite - basic suite Failed test/failed phase Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine-nodejs-modules) ] [ 27-02-2019 ] [ 002_bootstrap.add_vm2_lease ]
by Dafna Ron 10 Mar '19

10 Mar '19

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/artifa… 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=::ffff: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 "<string>", 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 2019-02-27 13:37:21,988-0500 INFO (jsonrpc/1) [storage.TaskManager.Task] (Task='9c297d41-0aa7-4c74-b268-b710e666bc6c') aborting: Task is aborted: u'No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee' - code 100 (task:1181) 2019-02-27 13:37:21,988-0500 ERROR (jsonrpc/1) [storage.Dispatcher] FINISH lease_info error=No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee (dispatcher:87) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line 74, in wrapper result = ctask.prepare(func, *args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in wrapper return m(self, *a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1189, in prepare raise self.error NoSuchLease: No such lease 3500eb82-e5e2-4e24-b41c-ea02d9f6adee

5 9

[JIRA] (OVIRT-2694) some users list emails are still not being threaded properly (probably yahoo / html related)
by Liora Milbaum (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2694?page=com.atlassian.jira.… ] Liora Milbaum reassigned OVIRT-2694: ------------------------------------ Assignee: Liora Milbaum (was: infra) > some users list emails are still not being threaded properly (probably yahoo / html related) > -------------------------------------------------------------------------------------------- > > Key: OVIRT-2694 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2694 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Greg Sheremeta > Assignee: Liora Milbaum > Attachments: Selection_042.png, image.png, strahil original.pdf > > > some users list emails are still not being threaded properly (probably yahoo / html related) > All of Strahil's messages do this. See screenshots and original message dump attached. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98364, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '19

10 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98364,5 (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/98364/5 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/13345/

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2695: ------------------------------------- Here: https://docs.google.com/document/d/1UYwjJdZLvlLdbfV2izx4Qs8fjagG1FB-meqjOnC… > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 97030, 14 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '19

10 Mar '19

A system test invoked by the "ovirt-master" change queue including change 97030,14 (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/97030/14 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/13342/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #370
by jenkins＠jenkins.phx.ovirt.org 10 Mar '19

10 Mar '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/37…> Changes: [Galit Rosenthal] Nightly builds jobs for he-basic-ipv6_suite ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision fe1ffdd2713cf6fea1d37631b7b7cc4fba8d6524 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f fe1ffdd2713cf6fea1d37631b7b7cc4fba8d6524 # timeout=10 Commit message: "Nightly builds jobs for he-basic-ipv6_suite" > git rev-list --no-walk 27896049ffe1c8cc80346f7596e948086c275e99 # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins8158068874731989508.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 185, in __init__ raise MetaLinkRepoErrorParseFail, "File %s does not exist" %filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml does not exist + reposync_out='Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64 error was File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml.tmp is not XML' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Eyal Edri (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2695: ---------------------------------- Can you share the link? > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2269
by jenkins＠jenkins.phx.ovirt.org 10 Mar '19

10 Mar '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/59/95959/1:test --prune # timeout=10 > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins354109812899683677.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-base-fc29. Please verify its path and try again Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2695: ------------------------------------- [~eedri] already added it to [~lmilbaum(a)redhat.com]'s KB doc > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Eyal Edri (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2695: ---------------------------------- Barak, can you please add info how and where you cleared the cache for future reference so we can look up this ticket if needed in the future? thanks On Sun, Mar 10, 2019, 13:12 Barak Korren (oVirt JIRA) < > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2695: -------------------------------- Blocked By: user response Status: Blocked (was: To Do) blocking ticket on user response > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

2 1

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2695: ------------------------------------- [~nsoffer(a)redhat.com] I cleared the caches, please check that your jobs pass now > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2695: -------------------------------- Issue Type: Outage (was: By-EMAIL) > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2695: -------------------------------- Component/s: CI client projects Jenkins Slaves > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI client projects, Jenkins Slaves > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 97030, 14 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '19

10 Mar '19

A system test invoked by the "ovirt-master" change queue including change 97030,14 (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/97030/14 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/13338/

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2695?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2695: ----------------------------------- Assignee: Barak Korren (was: infra) > [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) > ------------------------------------------------------------------ > > Key: OVIRT-2695 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Barak Korren > > build-artifacts on s390x fail now with: > [Errno 2] No such file or directory: > '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' > Here are few example failures: > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… > This is going to block the change queue when we merge these patches, > and we have 4.3 build soon. > We had this issue few week ago, and Barak fixed this by deleting caches on > the slaves. I hope this can be fixed quickly > this time. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Barak Korren (oVirt JIRA) 10 Mar '19

10 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2252: ------------------------------------- we cannot, because of the way stdciv2 works, if we drop the slave, the jobs for the 'jenkins' repo will never finish. I wouldn't want to just drop the 'jenkins' repo jobs, because that is the only way we have ATM to pre-test some things. I think at this point the solution we should aim for is to containerize the s390x host, that would resolve this issue and would enable us to drop support for not-containerized hosts in the future. I actually had a chat with the host's maintainer a while ago, and he was willing to install docker there. The intiative died out because I did not have time to push it further. > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another. > The are several issues that are caused by this configuration: > # Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675. > # The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98364, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Mar '19

10 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98364,5 (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/98364/5 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/13336/

1 0

oVirt infra daily report - unstable production jobs - 759
by jenkins＠jenkins.phx.ovirt.org 10 Mar '19

10 Mar '19

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/759//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2252) The s390x slave is used in parallel by both the staging and the production CI systems
by Eyal Edri (oVirt JIRA) 09 Mar '19

09 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2252: ---------------------------------- Can we drop it from staging? its best to have one working slave on production and if we really need it on staging, we can ask for one more > The s390x slave is used in parallel by both the staging and the production CI systems > ------------------------------------------------------------------------------------- > > Key: OVIRT-2252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Since we only have one s390x slave, it is currently attached to both the staging and the production CI systems, and while they use separate user accounts, it turns out this is not enough to isolate them from one another. > The are several issues that are caused by this configuration: > # Tests that allocate a fixed network port can fail if they are run by both systems at the same time - this happens in practice when sending Python patchs to the '{{jenkins}}' repo because the {{mirror_client.py}} tests start a web server on port 8675. > # The {{mock_cleanup.sh}} script that is being run by one system can time out trying to umount things from a mock environment that was created and is being used by the other system. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2695) [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Nir Soffer (oVirt JIRA) 09 Mar '19

09 Mar '19

Nir Soffer created OVIRT-2695: --------------------------------- Summary: [VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?) Key: OVIRT-2695 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2695 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra build-artifacts on s390x fail now with: [Errno 2] No such file or directory: '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' Here are few example failures: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… This is going to block the change queue when we merge these patches, and we have 4.3 build soon. We had this issue few week ago, and Barak fixed this by deleting caches on the slaves. I hope this can be fixed quickly this time. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[VDSM] build-artifacts on s390x broken again (bad mock/dnf cache?)
by Nir Soffer 09 Mar '19

09 Mar '19

build-artifacts on s390x fail now with: [Errno 2] No such file or directory: '/var/cache/dnf/updates-07b7057ee4fded96/packages/systemd-238-12.git07f8cd5.fc28.s390x.rpm' Here are few example failures: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… This is going to block the change queue when we merge these patches, and we have 4.3 build soon. We had this issue few week ago, and Barak fixed this by deleting caches on the slaves. I hope this can be fixed quickly this time. Nir

1 0

oVirt infra daily report - unstable production jobs - 758
by jenkins＠jenkins.phx.ovirt.org 09 Mar '19

09 Mar '19

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/758//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 98364, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Mar '19

08 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98364,5 (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/98364/5 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/13331/

1 0

[JIRA] (OVIRT-2694) some users list emails are still not being threaded properly (probably yahoo / html related)
by Greg Sheremeta (oVirt JIRA) 08 Mar '19

08 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2694?page=com.atlassian.jira.… ] Greg Sheremeta updated OVIRT-2694: ---------------------------------- Attachment: image.png > some users list emails are still not being threaded properly (probably yahoo / html related) > -------------------------------------------------------------------------------------------- > > Key: OVIRT-2694 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2694 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_042.png, image.png, strahil original.pdf > > > some users list emails are still not being threaded properly (probably yahoo / html related) > All of Strahil's messages do this. See screenshots and original message dump attached. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2694) some users list emails are still not being threaded properly (probably yahoo / html related)
by Greg Sheremeta (oVirt JIRA) 08 Mar '19

08 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2694?page=com.atlassian.jira.… ] Greg Sheremeta updated OVIRT-2694: ---------------------------------- Attachment: Selection_042.png > some users list emails are still not being threaded properly (probably yahoo / html related) > -------------------------------------------------------------------------------------------- > > Key: OVIRT-2694 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2694 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_042.png, image.png, strahil original.pdf > > > some users list emails are still not being threaded properly (probably yahoo / html related) > All of Strahil's messages do this. See screenshots and original message dump attached. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2694) some users list emails are still not being threaded properly (probably yahoo / html related)
by Greg Sheremeta (oVirt JIRA) 08 Mar '19

08 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2694?page=com.atlassian.jira.… ] Greg Sheremeta updated OVIRT-2694: ---------------------------------- Attachment: strahil original.pdf > some users list emails are still not being threaded properly (probably yahoo / html related) > -------------------------------------------------------------------------------------------- > > Key: OVIRT-2694 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2694 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Greg Sheremeta > Assignee: infra > Attachments: Selection_042.png, image.png, strahil original.pdf > > > some users list emails are still not being threaded properly (probably yahoo / html related) > All of Strahil's messages do this. See screenshots and original message dump attached. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2694) some users list emails are still not being threaded properly (probably yahoo / html related)
by Greg Sheremeta (oVirt JIRA) 08 Mar '19

08 Mar '19

Greg Sheremeta created OVIRT-2694: ------------------------------------- Summary: some users list emails are still not being threaded properly (probably yahoo / html related) Key: OVIRT-2694 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2694 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Greg Sheremeta Assignee: infra some users list emails are still not being threaded properly (probably yahoo / html related) All of Strahil's messages do this. See screenshots and original message dump attached. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98371, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Mar '19

08 Mar '19

A system test invoked by the "ovirt-master" change queue including change 98371,2 (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/98371/2 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/13327/

1 0

[CQ]: 98375,1 (imgbased) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Mar '19

08 Mar '19

Change 98375,1 (imgbased) 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/98375/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/165/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 08 Mar '19

08 Mar '19

Failed to run project_setup.sh for: #3706 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0100.workers-phx.ovirt.org.

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 504 - Failure!
by jenkins＠jenkins.phx.ovirt.org 08 Mar '19

08 Mar '19

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/504/ Build Number: 504 Build Status: Failure 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 ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 505 - Failure!
by jenkins＠jenkins.phx.ovirt.org 08 Mar '19

08 Mar '19

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/505/ Build Number: 505 Build Status: Failure 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. ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 757
by jenkins＠jenkins.phx.ovirt.org 08 Mar '19

08 Mar '19

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-a… Cheers, Jenkins

1 0

[CQ]: 98191, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Mar '19

07 Mar '19

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/

1 0

error failed to execute stage 'misc configuration': failed to start service 'openvswitch'
by katiam＠softel.cu 07 Mar '19

07 Mar '19

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?

1 0

[CQ]: 97381,22 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 07 Mar '19

07 Mar '19

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/

1 0

[CQ]: 10a3041 (ovirt-ansible-shutdown-env) failed "ovirt-4.3" system tests
by oVirt Jenkins 07 Mar '19

07 Mar '19

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/10a3041ed9833209… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/156/

1 0

[CQ]: 95460, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Mar '19

07 Mar '19

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/

1 0