- Infra - oVirt List Archives

[JIRA] (OVIRT-2400) check-patch failed on he-basic-iscsi-master with 'disk_space requirements are not satisfied'
by Dafna Ron (oVirt JIRA) 09 Aug '18

09 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2400?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2400: ----------------------------- Labels: ost_failures ost_infra ost_lago (was: ost_failures ost_lago) > check-patch failed on he-basic-iscsi-master with 'disk_space requirements are not satisfied' > -------------------------------------------------------------------------------------------- > > Key: OVIRT-2400 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2400 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_lago > > https://pastebin.com/HfpwWfgi > we have 3 disks: Main NFS device (101G), Main iSCSI device (191G) and Hosted engine storage (80G) > > Gal, should we increase the 80- GB to 101 as well? > Adding patch - if needed please merge: https://gerrit.ovirt.org/93493 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2402) ioprocess failed ovirt-master with 500 error from engine
by Dafna Ron (oVirt JIRA) 09 Aug '18

09 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2402?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2402: ----------------------------- Labels: ost_failures ost_race (was: ost_failures) > ioprocess failed ovirt-master with 500 error from engine > -------------------------------------------------------- > > Key: OVIRT-2402 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2402 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > 004_basic_sanity.run_vms failed with Internal Server Error from engine. > Looking at engine and server logs I actually do not see any issue with engine or the machine itself but there is a 500 reply to the API. > I think the issue is that the api got a 500 reply from engine but I am not seeing a reason why so this needs to be investigated further. > I am keeping build logs and will look at it later on > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8971/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2403) failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite
by Dafna Ron (oVirt JIRA) 09 Aug '18

09 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2403?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2403: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2403 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2403 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > this is related to patch which was reported by CQ; > https://gerrit.ovirt.org/#/c/93466/ - core: clean stale image_transfer on upgrade > Link to Job: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975 > '[ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0270_add_foreign_key_to_image_transfers.sql' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2403) failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite
by Dafna Ron (oVirt JIRA) 09 Aug '18

09 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2403?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2403: ---------------------------------- ovirt-engine has passed on master so issue is resolved. closing ticket > failure on ovirt-master for test 001_upgrade_engine.test_initialize_engine on upgrade suite > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2403 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2403 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > this is related to patch which was reported by CQ; > https://gerrit.ovirt.org/#/c/93466/ - core: clean stale image_transfer on upgrade > Link to Job: > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8975 > '[ ERROR ] schema.sh: FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/dbscripts/upgrade/04_03_0270_add_foreign_key_to_image_transfers.sql' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2404) CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo
by Dafna Ron (oVirt JIRA) 09 Aug '18

09 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2404?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2404: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > CQ 4.2 vdsm failing upgrade-from-prevrelease-suite on missing 4.1 tested repo > ----------------------------------------------------------------------------- > > Key: OVIRT-2404 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2404 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > https://pastebin.com/uMQMjAq5 > we are failing since 4.1 tested is missing. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2774/consoleFull > patch that failed is not related to the issue but this is the one that failed: > https://gerrit.ovirt.org/#/c/93253/3 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 07-08-2018 ] [ 004_basic_sanity.update_template_version ]
by Dafna Ron 09 Aug '18

09 Aug '18

Hi, We are failing ovirt 4.2 on project ovirt-engine on test 004_basic_sanity.update_template_version. I believe the reported patch from CQ may have indeed caused the issue. Eli, can you please check this issue? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/93501/ <https://gerrit.ovirt.org/#/c/93501/> - * *core:make search string fields not null and emptyLink to Job:https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800 <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800>Link to all logs:https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800/artif… <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2800/artifact/b…>(Relevant) error snippet from the log: <error><JsonRpcRequest id: "0aec9ef2-5e1f-4cb6-bf75-f5826d2ae135", method: Volume.getInfo, params: {storagepoolID=fe6f6819-4791-4624-aa56-c82e49b0eaf3, storagedomainID=2a3af2d0-c00e-4ac7-a162-fa08d33c173f, imageID=2d2f61d4-2347-4200-9c1f-0ee376104ef0, volumeID=21ea717f-e3a1-4c36-8101-ba746bd78c40}>2018-08-07 06:12:46,522-04 INFO [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] Running command: AddVmTemplateCommand internal: false. Entities affected : ID: fe6f6819-4791-4624-aa56-c82e49b0eaf3 Type: StoragePoolAction group CREATE_TEMPLATE with role type USER2018-08-07 06:12:46,525-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] START, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='64293490-e128-48b7-9e23-0491b48d9a1f', status='ImageLocked', exitStatus='Normal'}), log id: eca02a92018-08-07 06:12:46,527-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] FINISH, SetVmStatusVDSCommand, log id: eca02a92018-08-07 06:12:46,527-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] method: runVdsCommand, params: [SetVmStatus, SetVmStatusVDSCommandParameters:{vmId='64293490-e128-48b7-9e23-0491b48d9a1f', status='ImageLocked', exitStatus='Normal'}], timeElapsed: 3ms2018-08-07 06:12:46,537-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] (default task-4) [6db41b0d-0d11-4b75-94f9-4a478e6fb3dc] Translating SQLException with SQL state '23502', error code '0', message [ERROR: null value in column "description" violates not-null constraint Detail: Failing row contains (ce532690-2131-49a8-b2a0-183936727092, CirrOS_0.4.0_for_x86_64_glance_template, 512, 5b1f874d-dc92-43ed-86ef-a9c2d6bfc9a3, 0, null, fe7292a4-c998-4f6c-897c-fa7525911a16, 2018-08-07 06:12:46.529-04, 1, null, f, 1, 1, 1, Etc/GMT, t, f, 2018-08-07 06:12:46.530974-04, null, null, f, 1, 0, 0, 1, 0, , 3, null, null, null, 0, , , 256, TEMPLATE, 0, 1, 31a8e1fa-1fad-456c-8b8a-aa11551cae9d, f, null, f, f, 1, f, f, f, d0d66980-9a26-11e8-b2f3-5452c0a8c802, null, , f, 0, null, null, null, guest_agent, null, null, null, 2, null, 2, 12345678, f, interleave, t, t, deb3f53e-13c5-4aea-bf90-0339eba39fed, null, null, null, null, 22716173-2816-a109-1d2f-c44d945e92dd, 3b3f239c-d8bb-423f-a39c-e2b905473b83, null, 1, LOCK_SCREEN, 2, null, null, 2048, null, AUTO_RESUME, t). Where: SQL statement "INSERT INTO vm_static( child_count, creation_date, description, free_text_comment, mem_size_mb, max_memory_size_mb, num_of_io_threads, vm_name, num_of_sockets, cpu_per_socket, threads_per_cpu, os, vm_guid, cluster_id, num_of_monitors, single_qxl_pci, allow_console_reconnect, template_status, usb_policy, time_zone, fail_back, vm_type, nice_level, cpu_shares, default_boot_sequence, default_display_type,* *</error>*

3 4

[JIRA] (OVIRT-2417) upgrade-from-prevrelease-suite failure *.repo No such file or directory
by Daniel Belenky (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2417?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2417: ---------------------------------- Resolution: Done Status: Done (was: To Do) Closing as this is not a bug. I've updated the version table helper https://gerrit.ovirt.org/#/c/93590/ Thanks for reporting this [~gshereme(a)redhat.com] > upgrade-from-prevrelease-suite failure *.repo No such file or directory > ----------------------------------------------------------------------- > > Key: OVIRT-2417 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2417 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST Manual job > Reporter: Greg Sheremeta > Assignee: infra > Priority: Highest > > Hi, > Re: packaging: Replace dashboard with ui-extensions > https://gerrit.ovirt.org/#/c/92698/ > As Didi requested, I tried to run upgrade-from-prevrelease-suite but: > *23:45:23* + cp > 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo' > exported-artifacts*23:45:23* cp: cannot stat > 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo': No > such file or directory*23:45:23* POST BUILD TASK : FAILURE*23:45:23* > END OF POST BUILD TASK : 0*23:45:23* ESCALATE FAILED POST BUILD TASK > TO JOB STATUS > Can you assist? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93545,1 (imgbased) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 Aug '18

08 Aug '18

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

2 1

[JIRA] (OVIRT-2417) upgrade-from-prevrelease-suite failure *.repo No such file or directory
by Daniel Belenky (oVirt JIRA) 08 Aug '18

08 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2417?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2417: --------------------------------------- [~gshereme(a)redhat.com] Upgrade from prevrelease-suite-master doesn't exist. You probably want to test upgrade from 4.2->master which is upgrade from release_suite master (currently, master is not considered a 'release'). There was a discussion on this topic here OVIRT-2091. > upgrade-from-prevrelease-suite failure *.repo No such file or directory > ----------------------------------------------------------------------- > > Key: OVIRT-2417 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2417 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST Manual job > Reporter: Greg Sheremeta > Assignee: infra > Priority: Highest > > Hi, > Re: packaging: Replace dashboard with ui-extensions > https://gerrit.ovirt.org/#/c/92698/ > As Didi requested, I tried to run upgrade-from-prevrelease-suite but: > *23:45:23* + cp > 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo' > exported-artifacts*23:45:23* cp: cannot stat > 'ovirt-system-tests/upgrade-from-prevrelease-suite-master/*.repo': No > such file or directory*23:45:23* POST BUILD TASK : FAILURE*23:45:23* > END OF POST BUILD TASK : 0*23:45:23* ESCALATE FAILED POST BUILD TASK > TO JOB STATUS > Can you assist? > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2418) CQ failure in ovirt-4.2 for project imgbased in test 004_basic_sanity.check_snapshot_with_memory
by Dafna Ron (oVirt JIRA) 08 Aug '18

08 Aug '18

Dafna Ron created OVIRT-2418: -------------------------------- Summary: CQ failure in ovirt-4.2 for project imgbased in test 004_basic_sanity.check_snapshot_with_memory Key: OVIRT-2418 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2418 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We failed patch https://gerrit.ovirt.org/#/c/93545/ - core: remove lvs after a failed upgrade on ovirt-4.2 The test that failed was 004_basic_sanity.check_snapshot_with_memory. this is the failed build: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/ looking at the patch, there is a chance that it created a failure in ost as registering the full size of an lvs may cause engine to think there is not enough disk space and fail the test. the storage is the iscsi storage (57395856-41dd-4617-be38-5ab3a7dcbc07) and I am not seeing low disk space on vdsm. I can see: 'u'57395856-41dd-4617-be38-5ab3a7dcbc07': {'status': u'Active', 'diskfree': '4294967296', 'isoprefix': '', 'alerts': [], 'disktotal': '21072183296', 'version': 4}}}' Here is the full getStoragePoolInfo output: '2018-08-08 09:47:02,489-0400 INFO (jsonrpc/5) [vdsm.api] FINISH getStoragePoolInfo return={'info': {'name': 'No Description', 'isoprefix': '', 'pool_status': 'connected', 'lver': 2L, 'domains': u'63a95d52-2309-43b7-8c91-c81c7c87b4c3:Acti ve,676d27b7-e7c7-419d-9a6a-ef6f1cecde85:Active,407bb2af-ae33-40d0-adb9-87c3732b0ce7:Active,57395856-41dd-4617-be38-5ab3a7dcbc07:Active', 'master_uuid': '57395856-41dd-4617-be38-5ab3a7dcbc07', 'version': '4', 'spm_id': 1, 'type': 'ISCSI', 'master_ver': 1}, 'dominfo': {u'63a95d52-2309-43b7-8c91-c81c7c87b4c3': {'status': u'Active', 'diskfree': '101063327744', 'isoprefix': '', 'alerts': [], 'disktotal': '106611867648', 'version': 4}, u'676d27b7-e7c7-419d-9a6a-ef6f1cecde85': { 'status': u'Active', 'diskfree': '101063327744', 'isoprefix': '', 'alerts': [], 'disktotal': '106611867648', 'version': 0}, u'407bb2af-ae33-40d0-adb9-87c3732b0ce7': {'status': u'Active', 'diskfree': '101063327744', 'isoprefix': '', 'alert s': [], 'disktotal': '106611867648', 'version': 4}, u'57395856-41dd-4617-be38-5ab3a7dcbc07': {'status': u'Active', 'diskfree': '4294967296', 'isoprefix': '', 'alerts': [], 'disktotal': '21072183296', 'version': 4}}} from=::ffff:192.168.20 0.2,45296, task_id=2e4ee839-8527-4cdc-b53f-8623346044e9 (api:52) ' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0