June 2019 - Infra - oVirt List Archives

Fwd: Announcing Fedora CI SIG
by Sandro Bonazzola 03 Jun '19

03 Jun '19

FYI ---------- Forwarded message --------- Da: Aleksandra Fedorova <alpha(a)bookwar.info> Date: ven 17 mag 2019 alle ore 14:20 Subject: Announcing Fedora CI SIG To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, <ci(a)lists.fedoraproject.org> Hi, all, I'd like to announce a Fedora Special Interest Group dedicated to the topics of Continuous Integration, Continuous Delivery, Gating and everything. I've created a wiki page with the initial data: https://fedoraproject.org/wiki/SIGs/CI Please join, add yourself to member list, bring your ideas and work items. I'd like to also setup a bi-weekly IRC meeting, so please think about what time would work best for you. Let's have a separate discussion on that next week. Feedback is welcome. Quote from the wiki: == Goal == The goal of the SIG is to bring together CI enthusiasts interested in developing tools, best practices, standards, and workflows to implement Continuous Integration at a larger scale. While CI is well-known and used by many software projects, it is usually applied at an individual component level. Scaling it up is a challenge from both technical and organizational points of view. Here in Fedora, we have an opportunity to explore and develop the CI/CD topic beyond simple pull-request testing. == Topics == * CI for Fedora * Containerized CI * CI on bare-metal * Gating at scale * Packaging and CI * CI and Upstream * CI engines, Artifact storages, Test analytics == Benefit to Fedora == CI is rarely associated with packaged Linux distributions even though it is nowadays used in most of them. We’d like to change this perception, to show that packaging and CI can and should be used together. We also would like to establish Fedora as a perfect CI platform. Virtualization, containerization and many other tools available in Fedora provide a good foundation to build flexible, open and modern CI solutions and CI architectures on top of it. Let's make use of them. -- Aleksandra Fedorova bookwar on IRC _______________________________________________ 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> <https://redhat.com/summit>

1 0

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #626
by jenkins＠jenkins.phx.ovirt.org 03 Jun '19

03 Jun '19

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/626/display/red…>

1 4

oVirt infra daily report - unstable production jobs - 844
by jenkins＠jenkins.phx.ovirt.org 03 Jun '19

03 Jun '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/844//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 100431, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Jun '19

02 Jun '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 595 - Failure!
by jenkins＠jenkins.phx.ovirt.org 02 Jun '19

02 Jun '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/595/ Build Number: 595 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #595 [Eitan Raviv] networking: test display network & console on ipv6 [Sandro Bonazzola] cockpit-ovirt: drop 4.3.z branch jobs [Sandro Bonazzola] cockpit-ovirt: add fc29 jobs on master [Barak Korren] collect_artifacts: Use createrepo_c ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.run_vms_42 Error Message: False != True after 600 seconds Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/004_basic_sanity.py", line 710, in run_vms lambda: api.vms.get(VM0_NAME).status.state == 'up' and api.vms.get(BACKUP_VM_NAME).status.state == 'up', File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 286, in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 273, in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 600 seconds

1 2

[CQ]: 100377, 2 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests
by oVirt Jenkins 02 Jun '19

02 Jun '19

Change 100377,2 (ovirt-engine-ui-extensions) 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/100377/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14418/

1 0

[CQ]: d383bb7 (ovirt-ansible-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 02 Jun '19

02 Jun '19

Change d383bb7 (ovirt-ansible-engine-setup) 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://github.com/oVirt/ovirt-ansible-engine-setup/commit/d383bb7c1b6a68c2… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14412/

1 0

oVirt infra daily report - unstable production jobs - 843
by jenkins＠jenkins.phx.ovirt.org 02 Jun '19

02 Jun '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/843//artifact/exported-a… Cheers, Jenkins

1 0

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

02 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100322,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100312,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100312,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100322/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100312/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14406/

1 0

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

01 Jun '19

A system test invoked by the "ovirt-master" change queue including change 100213,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 100312,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 100312,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100213/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/100312/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14400/

1 0

[CQ]: 100406, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Jun '19

01 Jun '19

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

1 0

[CQ]: 100424, 1 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Jun '19

01 Jun '19

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

1 0