- Infra - oVirt List Archives

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2725: ----------------------------------- On Sun, May 12, 2019 at 6:32 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> I had this failure in yum install: >> >> [2019-05-12T14:54:55.706Z] Error Summary >> [2019-05-12T14:54:55.706Z] ------------- >> [2019-05-12T14:54:55.706Z] Disk Requirements: >> [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / >> filesystem. >> >> Build: >> >> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >> >> Trying build again, hopefully will get a slave with more space... >> > > Unfortunately, I got the same slave again: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Another failure: https://jenkins.ovirt.org/job/standard-manual-runner/249/ > > This blocks urgent bug: > https://bugzilla.redhat.com/1700623 > > Nir > > > >> >> Nir >> > > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

3 2

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2725: ---------------------------------- You s390x build is failing, its the only VM we have. I cleaned up the space there. it should work now. On Sun, May 12, 2019 at 6:44 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, May 12, 2019 at 6:32 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> I had this failure in yum install: >>> >>> [2019-05-12T14:54:55.706Z] Error Summary >>> [2019-05-12T14:54:55.706Z] ------------- >>> [2019-05-12T14:54:55.706Z] Disk Requirements: >>> [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / >>> filesystem. >>> >>> Build: >>> >>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >>> >>> Trying build again, hopefully will get a slave with more space... >>> >> >> Unfortunately, I got the same slave again: >> >> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… >> > > Another failure: > https://jenkins.ovirt.org/job/standard-manual-runner/249/ > > >> >> This blocks urgent bug: >> https://bugzilla.redhat.com/1700623 >> >> Nir >> >> >> >>> >>> Nir >>> >> -- Eyal edri MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2725: ---------------------------------- I cleaned up the slave using: mock -r ./fedora-28-s390x.cfg --shell rm -rfv /hostvar/cache/mock/fedora-??-s390x-* I think this slave isn't cleaned up because we don't have sudo on it. perhaps a local cleanup script can help. On Sun, May 12, 2019 at 6:46 PM Nir Soffer (oVirt JIRA) < -- Eyal edri MANAGER CONTINUOUS PRODUCTIZATION SYSTEM ENGINEERING Red Hat <https://www.redhat.com/> <https://red.ht/sig> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel) > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-2725: ----------------------------------- On Sun, May 12, 2019 at 6:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > I had this failure in yum install: > > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > > Build: > > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > > Trying build again, hopefully will get a slave with more space... > Unfortunately, I got the same slave again: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… This blocks urgent bug: https://bugzilla.redhat.com/1700623 Nir > > Nir > > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Nir Soffer (oVirt JIRA) 12 May '19

12 May '19

Nir Soffer created OVIRT-2725: --------------------------------- Summary: Build artifacts failed - not enough free space on file system Key: OVIRT-2725 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I had this failure in yum install: [2019-05-12T14:54:55.706Z] Error Summary [2019-05-12T14:54:55.706Z] ------------- [2019-05-12T14:54:55.706Z] Disk Requirements: [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / filesystem. Build: https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… Trying build again, hopefully will get a slave with more space... Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100101)

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 May '19

12 May '19

Change 99533,1 (ovirt-vmconsole) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/99533/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4323/

4 5

oVirt infra daily report - unstable production jobs - 822
by jenkins＠jenkins.phx.ovirt.org 11 May '19

11 May '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/822//artifact/exported-a… Cheers, Jenkins

1 0

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

10 May '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/821//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 May '19

10 May '19

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

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 10-05-2019 ] [ 004_basic_sanity.vm_run ]
by Dafna Ron 10 May '19

10 May '19

Hi, We are failing upgrade-from-release-suite.el7.x86_64 / 004_basic_sanity.vm_run The issue is an unexpected exception in vdsm. root cause based on CQ is this patch: https://gerrit.ovirt.org/#/c/99854/ - yum: Allow downloading only 'vdsm' package Logs can be found here: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14079/artifac… Marcin, can you please take a look? error: vdsm: 2019-05-10 05:06:38,329-0400 ERROR (jsonrpc/0) [api] FINISH create error=Unexpected exception (api:131) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 124, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 245, in create raise exception.UnexpectedError() UnexpectedError: Unexpected exception 2019-05-10 05:06:38,330-0400 INFO (jsonrpc/0) [api.virt] FINISH create return={'status': {'message': 'Unexpected exception', 'code': 16}} from=::ffff:192.168.201.2,39486, flow_id=83e4f0c4-a39a-45aa-891f-4022765e1a87, vmId=397013a0-b7d4-4d38-86c3-e944cebd75a7 (api:54) 2019-05-10 05:06:38,331-0400 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call VM.create failed (error 16) in 0.00 seconds (__init__:312) 2019-05-10 05:06:38,629-0400 INFO (jsonrpc/7) [vdsm.api] FINISH getStorageDomainInfo return={'info': {'uuid': '24498263-8985-46a9-9161-f65ee776cb7f', 'vgMetadataDevice': '360014051f333158820a4cc6ab3be5b55', 'vguuid': 'rXTLNc-JwEz-0dtL-Z2EC-ASqn-gzkg-jDJa1b', 'metadataDevice': '360014051f333158820a4cc6ab3be5b55', 'state': 'OK', 'version': '4', 'role': 'Master', 'type': 'ISCSI', 'class': 'Data', 'pool': ['3e330122-c587-4078-b9a4-13dbb697c5cc'], 'name': 'iscsi'}} from=::ffff:192.168.201.2,39486, flow_id=3f76d32a, task_id=084e7ee5-3c43-4905-833f-9a522043a862 (api:54) engine: 2019-05-10 05:06:38,328-04 ERROR [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] VDS::create Failed creating vm 'v m0' in vds = '566eda0f-3ef0-4791-a618-1e649af4b0be' error = 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to C reateBrokerVDS, error = Unexpected exception, code = 16' 2019-05-10 05:06:38,328-04 INFO [org.ovirt.engine.core.vdsbroker.CreateVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] FINISH, CreateVDSCommand, return: Down, log id: 3cb7c62d 2019-05-10 05:06:38,328-04 WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Failed to run VM 'vm0': EngineException: or g.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to CreateBrokerVDS, error = Unexpected exception, code = 16 (Failed with error unexpected and code 16) 2019-05-10 05:06:38,328-04 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Lock freed to object 'EngineLock:{exclu siveLocks='[397013a0-b7d4-4d38-86c3-e944cebd75a7=VM]', sharedLocks=''}' 2019-05-10 05:06:38,329-04 INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Trying to rerun VM 'vm0' 2019-05-10 05:06:38,373-04 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] EVENT_ID: USE R_INITIATED_RUN_VM_FAILED(151), Failed to run VM vm0 on Host lago-upgrade-from-release-suite-master-host-0. 2019-05-10 05:06:38,381-04 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Lock Acquired to object 'EngineLock:{ex clusiveLocks='[397013a0-b7d4-4d38-86c3-e944cebd75a7=VM]', sharedLocks=''}' 2019-05-10 05:06:38,393-04 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] START, IsVmDuringIn itiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='397013a0-b7d4-4d38-86c3-e944cebd75a7'}), log id: 96be328 2019-05-10 05:06:38,393-04 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] FINISH, IsVmDuringI nitiatingVDSCommand, return: false, log id: 96be328 2019-05-10 05:06:38,403-04 WARN [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Validation of action 'RunVmOnce' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS 2019-05-10 05:06:38,404-04 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] Lock freed to object 'EngineLock:{exclu siveLocks='[397013a0-b7d4-4d38-86c3-e944cebd75a7=VM]', sharedLocks=''}' 2019-05-10 05:06:38,413-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [83e4f0c4-a39a-45aa-891f-4022765e1a87] EVENT_ID: USE R_FAILED_RUN_VM(54), Failed to run VM vm0 (User: admin@internal-authz). 2019-05-10 05:06:38,462-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [There are no hosts to use. Check that the cluster contains at least one host in Up state.] 2019-05-10 05:06:38,466-04 INFO [org.ovirt.engine.core.bll.ProcessDownVmCommand] (EE-ManagedThreadFactory-engine-Thread-35) [3f40b3e8] Running command: ProcessDownVmCommand internal: true. Thanks, Dafna

3 4