- Infra - oVirt List Archives

[CQ]: 91077,13 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 25 May '18

25 May '18

Change 91077,13 (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/91077/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7752/

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 151 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-pre_build-artifacts-… Build Number: 151 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #151 [Miguel Duarte Barroso] Adding myself to the list [Evgheni Dereveanchin] Ensure nested KVM is enabled from global_setup [Daniel Belenky] Update legend table of manual OST [Emil Natan] refactor formatters code [Barak Korren] Add jobs for 'jniederm' user on GitHub [Gal Ben Haim] lago: Add fc28 build, drop fc26 build [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Daniel Belenky] Inject git config name and email in std template [Eyal Edri] drop all 4.1 nightly ost jobs [Daniel Belenky] Remove aspostrophes from git-config params [Eyal Edri] Drop obselete gluster 3.7,3.8 repos from mirrors [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran.

1 2

[CQ]: 91538,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 25 May '18

25 May '18

Change 91538,4 (ovirt-engine-sdk) 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/91538/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7747/

1 0

[CQ]: 91500,3 (imgbased) failed "ovirt-master" system tests
by oVirt Jenkins 24 May '18

24 May '18

Change 91500,3 (imgbased) 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/91500/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7741/

1 0

[oVirt Jenkins] ovirt-appliance_4.1_build-artifacts-el7-x86_64 - Build # 65 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 May '18

24 May '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_4.1_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_4.1_build-artifacts-el7-x86_64… Build Number: 65 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #65 [Daniel Belenky] Inject git config name and email in std template [Eyal Edri] drop all 4.1 nightly ost jobs [Daniel Belenky] Remove aspostrophes from git-config params [Eyal Edri] Drop obselete gluster 3.7,3.8 repos from mirrors [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran.

1 14

[CQ]: 91525, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '18

24 May '18

A system test invoked by the "ovirt-master" change queue including change 91525,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91525/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7736/

1 0

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 24 May '18

24 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/155 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I245e8658317dc9ac36fb0e9607c5386255bae8f4 Gerrit-Change-Number: 155 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Thu, 24 May 2018 13:55:49 +0000 Gerrit-HasComments: No

1 0

Fwd: node-commits@ovirt.org post from sbonazzo@redhat.com requires approval
by Yaniv Kaul 24 May '18

24 May '18

---------- Forwarded message ---------- From: Perry Myers <pmyers(a)redhat.com> Date: Thu, May 24, 2018 at 3:09 PM Subject: Fwd: node-commits(a)ovirt.org post from sbonazzo(a)redhat.com requires approval To: Sandro Bonazzola <sbonazzo(a)redhat.com>, Yaniv Kaul <ykaul(a)redhat.com> Probably someone should take me off of the admin list for this :) I don't even think I can get into this list any longer to approve the message Cheers, Perry ---------- Forwarded message ---------- From: <root(a)ovirt.org> Date: Thu, May 24, 2018 at 7:52 AM Subject: node-commits(a)ovirt.org post from sbonazzo(a)redhat.com requires approval To: node-commits-owner(a)ovirt.org As list administrator, your authorization is requested for the following mailing list posting: List: node-commits(a)ovirt.org From: sbonazzo(a)redhat.com Subject: oVirt Privacy policy change The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request. ---------- Forwarded message ---------- From: Sandro Bonazzola <sbonazzo(a)redhat.com> To: announce(a)ovirt.org Cc: Bcc: Date: Thu, 24 May 2018 13:49:25 +0200 Subject: oVirt Privacy policy change *As part of an oVirt project review, we're publishing an updated privacy policy.You should read the statement fully, but the key updates include:* Clearer descriptions of how oVirt uses your personal data to provide services;* Additional detail on how your personal data may be shared to serve the public interest and that of the open source community; and* More focus on how you can review, modify, and update your personal data.You can find the new statement on the oVirt website at this location: https://ovirt.org/site/privacy-policy/ <https://ovirt.org/site/privacy-policy/>oVirt website pages have been updated to include links to the privacy policy. The new privacy statement takes effect on Friday, May 25, 2018. * -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit> ---------- Forwarded message ---------- From: node-commits-request(a)ovirt.org To: Cc: Bcc: Date: Thu, 24 May 2018 07:52:46 -0400 Subject: confirm c3a256e90c007274a6326608cb3c915530f019ab If you reply to this message, keeping the Subject: header intact, Mailman will discard the held message. Do this if the message is spam. If you reply to this message and include an Approved: header with the list password in it, the message will be approved for posting to the list. The Approved: header can also appear in the first line of the body of the reply.

2 1

[CQ]: 91507, 1 (ovirt-engine-sdk-java) failed "ovirt-master" system tests
by oVirt Jenkins 24 May '18

24 May '18

Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/

2 1

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]
by Dafna Ron 24 May '18

24 May '18

Hi, This failure seems to be related to the regression we found earlier today which was causing failure in initialize engine: https://gerrit.ovirt.org/#/c/89293/ - core:make search string fields not null and empty The fix for the above change was reported as failed on the update template test with an error which I think is related to the same regression. https://gerrit.ovirt.org/#/c/91476/ - db: resolve duplicate db scripts Can you please have a look? *Link to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/artifact…>(Relevant) error snippet from the log: <error>2018-05-22 12:40:21,015-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: runQuery, params: [GetSoundDevices, IdQueryParameters:{refresh='false', filtered='false'}], timeElapsed: 3ms2018-05-22 12:40:21,021-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: get, params: [5cf93146-a5f1-4330-affe-672eaf39cc0d], timeElapsed: 1ms2018-05-22 12:40:21,045-04 INFO [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] Lock Acquired to object 'EngineLock:{exclusiveLocks='[2f43ef56-db61-4d93-99ee-00e84c741a29=DISK, bb954b00-d22c-4421-aba2-35335f9c441f=TEMPLATE, 9d749a87-45c9-4251-8e69-e55da5d3deed=DISK]', sharedLocks='[5cf93146-a5f1-4330-affe-672eaf39cc0d=VM, 4c68925d-569d-4987-8f54-29859763391a=TEMPLATE]'}'2018-05-22 12:40:21,097-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: get, params: [5cf93146-a5f1-4330-affe-672eaf39cc0d], timeElapsed: 2ms2018-05-22 12:40:21,111-04 INFO [org.ovirt.engine.core.bll.AddVmTemplateCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] Running command: AddVmTemplateCommand internal: false. Entities affected : ID: 79448f95-c26c-45b6-b396-ecd8fe98c2d9 Type: StoragePoolAction group CREATE_TEMPLATE with role type USER2018-05-22 12:40:21,115-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] START, SetVmStatusVDSCommand( SetVmStatusVDSCommandParameters:{vmId='5cf93146-a5f1-4330-affe-672eaf39cc0d', status='ImageLocked', exitStatus='Normal'}), log id: 4897bb3a2018-05-22 12:40:21,117-04 INFO [org.ovirt.engine.core.vdsbroker.SetVmStatusVDSCommand] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] FINISH, SetVmStatusVDSCommand, return: , log id: 4897bb3a2018-05-22 12:40:21,117-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] method: runVdsCommand, params: [SetVmStatus, SetVmStatusVDSCommandParameters:{vmId='5cf93146-a5f1-4330-affe-672eaf39cc0d', status='ImageLocked', exitStatus='Normal'}], timeElapsed: 4ms2018-05-22 12:40:21,125-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.CustomSQLErrorCodeSQLExceptionTranslator] (default task-10) [aa79ad89-02ea-4474-ad41-78cf52243b41] Translating SQLException with SQL state '23502', error code '0', message [ERROR: null value in column "description" violates not-null constraint Detail: Failing row contains (bb954b00-d22c-4421-aba2-35335f9c441f, CirrOS_0.4.0_for_x86_64_glance_template, 512, 4c68925d-569d-4987-8f54-29859763391a, 0, null, 5e28a528-59ad-4054-9397-a9174ec356a7, 2018-05-22 12:40:21.119-04, 1, null, f, 1, 1, 1, Etc/GMT, t, f, 2018-05-22 12:40:21.120272-04, null, null, f, 1, 0, 0, 1, 0, , 3, null, null, null, 0, , , 256, TEMPLATE, 0, 1, 7d498f3a-b16d-4574-9e47-9c87cd1c866b, f, null, f, f, 1, f, f, f, bd48ab26-5ddb-11e8-b3bb-5452c0a8c904, null, , f, 0, null, null, null, guest_agent, null, null, null, 2, null, 2, 12345678, f, interleave, t, t, 20fa3adb-29f2-4938-b07a-751d63a65447, null, null, null, 0, null, 3463183e-b5ce-076d-2a26-0e3e9d93dafb, d2f75033-25ec-e3b3-3c27-351115d4aa2b, null, 0, LOCK_SCREEN, 2, null, null, 2048, null, AUTO_RESUME). 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, priority, auto_startup, is_stateless, iso_path, origin, initrd_url, kernel_url, kernel_params, entity_type, quota_id, migration_support, is_disabled,dedicated_vm_for_vds, is_smartcard_enabled, is_delete_protected, sso_method, tunnel_migration, vnc_keyboard_layout, min_allocated_mem, is_run_and_pause, created_by_user_id, migration_downtime, template_version_number, vmt_guid, template_version_name, serial_number_policy, custom_serial_number, is_boot_menu_enabled, is_spice_file_transfer_enabled, is_spice_copy_paste_enabled, cpu_profile_id, numatune_mode, is_auto_converge, is_migrate_compressed, predefined_properties, userdefined_properties, custom_emulated_machine, bios_type, custom_cpu_name, small_icon_id, large_icon_id, console_disconnect_action, resume_behavior, custom_compatibility_version, migration_policy_id, lease_sd_id) VALUES( v_child_count, v_creation_date, v_description, v_free_text_comment, v_mem_size_mb, v_max_memory_size_mb, v_num_of_io_threads, v_name, v_num_of_sockets, v_cpu_per_socket, v_threads_per_cpu, v_os, v_vmt_guid, v_cluster_id, v_num_of_monitors, v_single_qxl_pci, v_allow_console_reconnect, v_status, v_usb_policy, v_time_zone, v_fail_back, v_vm_type, v_nice_level, v_cpu_shares, v_default_boot_sequence, v_default_display_type, v_priority, v_auto_startup, v_is_stateless, v_iso_path, v_origin, v_initrd_url, v_kernel_url, v_kernel_params, v_template_type, v_quota_id, v_migration_support, v_is_disabled, v_dedicated_vm_for_vds, v_is_smartcard_enabled, v_is_delete_protected, v_sso_method, v_tunnel_migration, v_vnc_keyboard_layout, v_min_allocated_mem, v_is_run_and_pause, v_created_by_user_id, v_migration_downtime, v_template_version_number, v_base_template_id, v_template_version_name, v_serial_number_policy, v_custom_serial_number, v_is_boot_menu_enabled, v_is_spice_file_transfer_enabled, v_is_spice_copy_paste_enabled, v_cpu_profile_id, v_numatune_mode, v_is_auto_converge, v_is_migrate_compressed, v_predefined_properties, v_userdefined_properties, v_custom_emulated_machine, v_bios_type, v_custom_cpu_name, v_small_icon_id, v_large_icon_id, v_console_disconnect_action, v_resume_behavior, v_custom_compatibility_version, v_migration_policy_id, v_lease_sd_id)"PL/pgSQL function insertvmtemplate(integer,timestamp with time zone,character varying,text,integer,integer,integer,character varying,integer,integer,integer,integer,uuid,uuid,integer,boolean,boolean,integer,integer,character varying,boolean,integer,integer,integer,integer,integer,integer,boolean,boolean,boolean,boolean,character varying,boolean,character varying,integer,character varying,character varying,character varying,uuid,integer,text,boolean,character varying,integer,boolean,uuid,character varying,integer,uuid,character varying,smallint,character varying,boolean,boolean,boolean,uuid,character varying,boolean,boolean,character varying,character varying,character varying,integer,character varying,uuid,uuid,character varying,character varying,character varying,uuid,uuid) line 16 at SQL statement]; SQL was [{call insertvmtemplate(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}] for task [CallableStatementCallback]</error>*

3 9

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Dafna Ron (oVirt JIRA) 24 May '18

24 May '18

Dafna Ron created OVIRT-2055: -------------------------------- Summary: failure in suspend resume vm not related to reported change - need to investigate Key: OVIRT-2055 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ I think the issue is on qemu/libvirt changed queries: https://pastebin.com/afyeUAcT https://pastebin.com/va20Y5Hp checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 24 May '18

24 May '18

Dafna Ron created OVIRT-2054: -------------------------------- Summary: false change reported since package is not deployed on ost Key: OVIRT-2054 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ The package is not deployed on OST so it could not have been the reason for failure. + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

oVirt Privacy policy change
by Sandro Bonazzola 24 May '18

24 May '18

*As part of an oVirt project review, we're publishing an updated privacy policy.You should read the statement fully, but the key updates include:* Clearer descriptions of how oVirt uses your personal data to provide services;* Additional detail on how your personal data may be shared to serve the public interest and that of the open source community; and* More focus on how you can review, modify, and update your personal data.You can find the new statement on the oVirt website at this location: https://ovirt.org/site/privacy-policy/ <https://ovirt.org/site/privacy-policy/>oVirt website pages have been updated to include links to the privacy policy. The new privacy statement takes effect on Friday, May 25, 2018. * -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

[CQ]: 91216, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '18

24 May '18

A system test invoked by the "ovirt-master" change queue including change 91216,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91216/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7730/

1 0

[oVirt Jenkins] ovirt-node-ng_4.1_build-artifacts-el7-x86_64 - Build # 64 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 May '18

24 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.1_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.1_build-artifacts-el7-x86_64/6… Build Number: 64 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #64 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran.

1 15

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc27-x86_64 #556
by jenkins＠jenkins.phx.ovirt.org 24 May '18

24 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_64…> Changes: [Daniel Belenky] global_setup to ensure ownership of ~/.ssh [Daniel Belenky] checkout_repo to tag every build ------------------------------------------ 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-updates-fc27-x86_64…> > 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 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 9e5273d12dda68e1fc306be58c3a26e3e3d66e30 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9e5273d12dda68e1fc306be58c3a26e3e3d66e30 Commit message: "checkout_repo to tag every build" > git rev-list --no-walk 73fa7d65045d749c46c791a74416adbba62fe887 # timeout=10 [system-sync_mirrors-fedora-updates-fc27-x86_64] $ /bin/bash -xe /tmp/jenkins3939764987152376278.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: fedora-updates-fc27 Syncing yum repo fedora-updates-fc27 for arch: x86_64 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 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-qemu-ev-release-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-qemu-ev-release-el7/gen' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 91461, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '18

24 May '18

A system test invoked by the "ovirt-master" change queue including change 91461,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91461/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7725/

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64 - Build # 634 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 May '18

24 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el… Build Number: 634 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #634 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran.

1 15

[oVirt Jenkins] ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 525 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 May '18

24 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x8… Build Number: 525 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #525 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Ryan Barry] image-update: fail upgrades if there is a local storage domain on / ----------------- Failed Tests: ----------------- No tests ran.

1 15

[JIRA] (OVIRT-2053) show release_branches information as part of STDCIv2 conf checker
by Emil Natan (oVirt JIRA) 24 May '18

24 May '18

Emil Natan created OVIRT-2053: --------------------------------- Summary: show release_branches information as part of STDCIv2 conf checker Key: OVIRT-2053 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2053 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Emil Natan Assignee: infra Show release_branches information as part of STDCIv2 configuration check utility -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91409, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '18

24 May '18

A system test invoked by the "ovirt-master" change queue including change 91409,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91409/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7716/

1 0

[CQ]: 91365, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 May '18

24 May '18

A system test invoked by the "ovirt-master" change queue including change 91365,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91365/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7711/

1 0

[CQ]: 91333, 11 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91333,11 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91333/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7706/

1 0

[CQ]: 91444, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91444,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91444/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7701/

1 0

oVirt infra weekly meeting notes 23.05.2018
by Evgheni Dereveanchin 23 May '18

23 May '18

Hi everyone, Please find the topics of this week's infra meeting below: *PHX DC: - CVE-2018-3639 OVIRT-2045 <https://ovirt-jira.atlassian.net/browse/OVIRT-2045>- Jenkins patched- Gerrit patched- Resources patched- Website patched- Jenkins core updated- SSL enabled on JenkinsMailMan: - Archive was incomplete - fixed by re-running cron job- UI issues - some settings not exposedAI: - Add links to https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> on our services- Create user for trello integration * -- Regards, Evgheni Dereveanchin

1 0

[CQ]: 91442, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91442,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91442/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7696/

1 0

[JIRA] (OVIRT-2052) Updated SSL Stores on resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 23 May '18

23 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2052?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2052: -------------------------------------- Assignee: Anton Marchukov (was: infra) > Updated SSL Stores on resources.ovirt.org > ----------------------------------------- > > Key: OVIRT-2052 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2052 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: Anton Marchukov > > resources.ovirt.org has old SSL stores and does not consider lets > encrypt certs as valid: > ovpn-205-70:~ amarchuk$ ssh http://resources.ovirt.org > ssh: Could not resolve hostname http://resources.ovirt.org: nodename > nor servname provided, or not known > ovpn-205-70:~ amarchuk$ ssh resources.ovirt.org > Last login: Thu May 10 14:19:17 2018 from monitoring.ovirt.org > [amarchuk@resources02 ~]$ curl https://jenkins.ovirt.org/ > curl: (60) Peer's Certificate issuer is not recognized. > More details here: http://curl.haxx.se/docs/sslcerts.html > curl performs SSL certificate verification by default, using a "bundle" > of Certificate Authority (CA) public keys (CA certs). If the default > bundle file isn't adequate, you can specify an alternate file > using the --cacert option. > If this HTTPS server uses a certificate signed by a CA represented in > the bundle, the certificate verification probably failed due to a > problem with the certificate (it might be expired, or the name might > not match the domain name in the URL). > If you'd like to turn off curl's verification of the certificate, use > the -k (or --insecure) option. > We also have a python utility called repoman that uses the bundle > certs inside “python-requests” library so we need to make sure it is > updated too along with the system certs. > We might have the same problem on other servers, e.g. on Jenkins and > it’s slaves so might make sense to analyse the situation and extend > this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2052) Updated SSL Stores on resources.ovirt.org
by Anton Marchukov (oVirt JIRA) 23 May '18

23 May '18

Anton Marchukov created OVIRT-2052: -------------------------------------- Summary: Updated SSL Stores on resources.ovirt.org Key: OVIRT-2052 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2052 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra resources.ovirt.org has old SSL stores and does not consider lets encrypt certs as valid: ovpn-205-70:~ amarchuk$ ssh http://resources.ovirt.org ssh: Could not resolve hostname http://resources.ovirt.org: nodename nor servname provided, or not known ovpn-205-70:~ amarchuk$ ssh resources.ovirt.org Last login: Thu May 10 14:19:17 2018 from monitoring.ovirt.org [amarchuk@resources02 ~]$ curl https://jenkins.ovirt.org/ curl: (60) Peer's Certificate issuer is not recognized. More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. We also have a python utility called repoman that uses the bundle certs inside “python-requests” library so we need to make sure it is updated too along with the system certs. We might have the same problem on other servers, e.g. on Jenkins and it’s slaves so might make sense to analyse the situation and extend this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[CQ]: 91441, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91441,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91441/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7691/

1 0

[JIRA] (OVIRT-2051) Re: Updated docs on oVirt site and Mail service
by eyal edri (oVirt JIRA) 23 May '18

23 May '18

eyal edri created OVIRT-2051: -------------------------------- Summary: Re: Updated docs on oVirt site and Mail service Key: OVIRT-2051 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2051 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri Assignee: infra Adding infra-support to open a ticket on it. On Sun, May 13, 2018 at 11:52 AM, Eyal Edri <eedri(a)redhat.com> wrote: > Hi, > > I was wondering if we have an official place where we keep docs on how we > manage the oVirt web site and mail server, in case we'll need to update or > debug an issue in any of the services. > > Ideally, we should have something under [1], can we add relevant links and > info there? > > [1] http://ovirt-infra-docs.readthedocs.io/en/latest/ > > -- > > Eyal edri > > > MANAGER > > RHV DevOps > > EMEA VIRTUALIZATION R&D > > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

Updated docs on oVirt site and Mail service
by Eyal Edri 23 May '18

23 May '18

Hi, I was wondering if we have an official place where we keep docs on how we manage the oVirt web site and mail server, in case we'll need to update or debug an issue in any of the services. Ideally, we should have something under [1], can we add relevant links and info there? [1] http://ovirt-infra-docs.readthedocs.io/en/latest/ -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 1

[oVirt CI] standard-enqueue - Build #13642 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 May '18

23 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13642/ Build Name: #13642 Build Description: Gerrit: 91512 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91512 - title: build: ovirt-engine-4.2.3.7 - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 1

[oVirt CI] standard-enqueue - Build #13640 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 May '18

23 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13640/ Build Name: #13640 Build Description: Gerrit: 91509 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91509 - title: core: add SSBD CPUs - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Michal Skrivanek <michal.skrivanek(a)redhat.com>

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1589
by jenkins＠jenkins.phx.ovirt.org 23 May '18

23 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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-updates-el7-x86_64/…> > 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 > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 73fa7d65045d749c46c791a74416adbba62fe887 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 73fa7d65045d749c46c791a74416adbba62fe887 Commit message: "Drop mock_runner support for FC25 and FC24" > git rev-list --no-walk 73fa7d65045d749c46c791a74416adbba62fe887 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins984243758019156706.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd 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 906, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 23 May '18

23 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/155 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I245e8658317dc9ac36fb0e9607c5386255bae8f4 Gerrit-Change-Number: 155 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 23 May 2018 08:36:07 +0000 Gerrit-HasComments: No

1 0

[CQ]: 91427, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 May '18

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91427,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91427/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7687/

1 0

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 23 May '18

23 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/155 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I245e8658317dc9ac36fb0e9607c5386255bae8f4 Gerrit-Change-Number: 155 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 23 May 2018 08:20:31 +0000 Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-2050) Make a landing page for STDCI builds
by Daniel Belenky (oVirt JIRA) 23 May '18

23 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2050?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2050: ---------------------------------- Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do) > Make a landing page for STDCI builds > ------------------------------------ > > Key: OVIRT-2050 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2050 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Since STDCI V2 executes the major build steps (running user script) on different nodes, it's hard to understand > the status/what failed from console output. The alternative is to use Blue Ocean view but it takes ~40 seconds to > load in some cases. > The first phase is to build a status report at the end of every STDCI build with quick access to relevant links such as logs, artifacts, test results and etc. > In the long term, the plan is to integrate "real time" updates such as console output updates per thread and etc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2050) Make a landing page for STDCI builds
by Daniel Belenky (oVirt JIRA) 23 May '18

23 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2050?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2050: ---------------------------------- Epic Link: OVIRT-400 > Make a landing page for STDCI builds > ------------------------------------ > > Key: OVIRT-2050 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2050 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Since STDCI V2 executes the major build steps (running user script) on different nodes, it's hard to understand > the status/what failed from console output. The alternative is to use Blue Ocean view but it takes ~40 seconds to > load in some cases. > The first phase is to build a status report at the end of every STDCI build with quick access to relevant links such as logs, artifacts, test results and etc. > In the long term, the plan is to integrate "real time" updates such as console output updates per thread and etc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2050) Make a landing page for STDCI builds
by Daniel Belenky (oVirt JIRA) 23 May '18

23 May '18

Daniel Belenky created OVIRT-2050: ------------------------------------- Summary: Make a landing page for STDCI builds Key: OVIRT-2050 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2050 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra Since STDCI V2 executes the major build steps (running user script) on different nodes, it's hard to understand the status/what failed from console output. The alternative is to use Blue Ocean view but it takes ~40 seconds to load in some cases. The first phase is to build a status report at the end of every STDCI build with quick access to relevant links such as logs, artifacts, test results and etc. In the long term, the plan is to integrate "real time" updates such as console output updates per thread and etc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

Planned restart of production services
by Evgheni Dereveanchin 23 May '18

23 May '18

Hi everyone, I will be restarting several production systems within the following hour to apply security updates. The following services may be unreachable for some period of time: - www.ovirt.org - project website - resources.ovirt.org - package repositories - gerrit.ovirt.org - code review - jenkins.ovirt.org - CI master It will not be possible to submit/review patches, clone repositories or run CI jobs during this period. Package repositories and the website will also be unreachable for a short period of time. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

2 2

[CQ]: 90819, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 May '18

22 May '18

A system test invoked by the "ovirt-master" change queue including change 90819,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/90819/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7682/

1 0

[CQ]: 91415, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 May '18

22 May '18

A system test invoked by the "ovirt-master" change queue including change 91415,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91415/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7678/

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.1_build-artifacts-el7-x86_64 - Build # 82 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 May '18

22 May '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1_build-artifacts-el7-… Build Number: 82 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #82 [Miguel Duarte Barroso] Adding myself to the list [Sandro Bonazzola] ovirt-host: add fc28 on master [Evgheni Dereveanchin] Verify IPv6 router advertisement settings from global_setup [Daniel Belenky] Inject git config name and email in std template [Eyal Edri] drop all 4.1 nightly ost jobs [Daniel Belenky] Remove aspostrophes from git-config params [Eyal Edri] Drop obselete gluster 3.7,3.8 repos from mirrors [Emil Natan] Collect STDCI logging functions into a separate module [Greg Sheremeta] add projects to stdci v2 [Emil Natan] Fix a bug with missing imports in stdci_logging.py [Daniel Belenky] Allow requirement of project specific nodes [Barak Korren] Fix Git user for 'jenkins' repo V1 jobs [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 91476, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 22 May '18

22 May '18

A system test invoked by the "ovirt-master" change queue including change 91476,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 89293,19 (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 89293,19 (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/91476/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7675/

1 0

[JIRA] (OVIRT-2049) review if SELinux can be enabled on CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 22 May '18

22 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2049?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2049: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > review if SELinux can be enabled on CI slaves > --------------------------------------------- > > Key: OVIRT-2049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Currently all CI slaves have SELinux set into Permissive mode. Opening this ticket to verify if that is still needed or if we can go with the default Enforcing setting. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2049) review if SELinux can be enabled on CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 22 May '18

22 May '18

Evgheni Dereveanchin created OVIRT-2049: ------------------------------------------- Summary: review if SELinux can be enabled on CI slaves Key: OVIRT-2049 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2049 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Currently all CI slaves have SELinux set into Permissive mode. Opening this ticket to verify if that is still needed or if we can go with the default Enforcing setting. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[oVirt CI] standard-enqueue - Build #13607 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 May '18

22 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13607/ Build Name: #13607 Build Description: Gerrit: 91496 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91496 - title: build: ovirt-engine-3.6.13.4 - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 1

[JIRA] (OVIRT-2048) regression on master caught
by Dafna Ron (oVirt JIRA) 22 May '18

22 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2048?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2048: -------------------------------- Assignee: Dafna Ron (was: infra) > regression on master caught > --------------------------- > > Key: OVIRT-2048 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2048 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > Labels: ost_code_regression, ost_failures > > Change 89293,19 (ovirt-engine) 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/89293/19 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7670/ > Speaking to Martin we already have a fix for this: https://gerrit.ovirt.org/91476 > waiting for the fix to pass and fix project before closing ticket. > Not reporting on list since we already know and have a fix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2048) regression on master caught
by Dafna Ron (oVirt JIRA) 22 May '18

22 May '18

Dafna Ron created OVIRT-2048: -------------------------------- Summary: regression on master caught Key: OVIRT-2048 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2048 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Change 89293,19 (ovirt-engine) 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/89293/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7670/ Speaking to Martin we already have a fix for this: https://gerrit.ovirt.org/91476 waiting for the fix to pass and fix project before closing ticket. Not reporting on list since we already know and have a fix. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0