February 2019 - Infra - Ovirt List Archives

oVirt infra daily report - unstable production jobs - 744

by jenkins＠jenkins.phx.ovirt.org

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/744//artifact/exported... Cheers, Jenkins

5 years, 2 months

1
0
0 / 0

Fwd: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC

by Sandro Bonazzola

FYI ---------- Forwarded message --------- From: Stephen John Smoogen <smooge(a)gmail.com> Date: ven 22 feb 2019 alle ore 20:43 Subject: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC To: <announce(a)lists.fedoraproject.org>, Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, Fedora Infrastructure < infrastructure(a)lists.fedoraproject.org> There will be an outage starting at 2019-02-27 20:00 UTC, which will last approximately 4-6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-27 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all core systems and services. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: All systems under fedoraproject.org will be affected. Important databases and authentication will be updated and rebooted first. Then other non-build systems will follow. Then build systems will finalize the update/reboot cycle Ticket Link: https://pagure.io/fedora-infrastructure/issue/7591 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

5 years, 2 months

1
0
0 / 0

[CQ]: 97986,1 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

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

5 years, 2 months

1
0
0 / 0

[Ovirt] [CQ weekly status] [22-02-2019]

by Dafna Ron

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: GREEN (#1) 1. rh-postgress was failing to start due to missing selinux policy causing engine to fail installation. Bug: https://bugzilla.redhat.com/show_bug.cgi Issue resolved by didi and Galit by: 1. adding a workaround to add the selinuc poslicy and also a proposed fix (as described in comment #6) 2. created new lago images with new selinux package *CQ-Master:* GREEN (#1) 1. The same issue in 4.2 has effected master (for upgrade suite) Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-... [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan... Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

5 years, 2 months

1
0
0 / 0

[CQ]: 1a0df55 (ovirt-ansible-engine-setup) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 1a0df55 (ovirt-ansible-engine-setup) 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://github.com/oVirt/ovirt-ansible-engine-setup/commit/1a0df550b30140... For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3930/

5 years, 2 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 491 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/491/ Build Number: 491 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #491 [jenkins CI] Add missing pkg: collectd-write_syslog [Sandro Bonazzola] ovirt-node-ng: stop building 4.2 and 4.2-pre [Gal Ben Haim] kubevirt-master: Add jobs [Tom�� Golembiovsk��] rename ovirt-ansible-v2v-conversion-host to v2v-conversion-host ----------------- Failed Tests: ----------------- No tests ran.

5 years, 2 months

1
1
0 / 0

oVirt infra daily report - unstable production jobs - 743

by jenkins＠jenkins.phx.ovirt.org

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/743//artifact/exported... Cheers, Jenkins

5 years, 2 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

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

5 years, 2 months

1
0
0 / 0

[CQ]: 92775,10 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

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

5 years, 2 months

1
0
0 / 0

[CQ]: 97847,5 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

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

5 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra February 2019