July 2019 - Infra - oVirt List Archives

[CQ]: 101572, 5 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 05 Jul '19

05 Jul '19

Change 101572,5 (ovirt-hosted-engine-ha) 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/101572/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14907/

1 0

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

05 Jul '19

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

1 0

[Ovirt] [CQ weekly status] [05-07-2019]
by Dafna Ron 05 Jul '19

05 Jul '19

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) Last failure was on 02-07 for ovirt-provider-ovm due to failed test: 098_ovirt_provider_ovn.use_ovn_provide. This was a code regression and was fixed by patch https://gerrit.ovirt.org/#/c/97072/ *CQ-4.3*: RED (#1) We are failing because our ost image is centos 7.6 and we now have 7.7 packages. Galit will need to create a new image to fix the failing tests. *CQ-Master:* RED (#1) We are failing because our ost image is centos 7.6 and we now have 7.7 packages. Galit will need to create a new image to fix the failing tests. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… 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)

1 0

[CQ]: 101570, 3 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jul '19

05 Jul '19

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

1 0

[CQ]: 101570, 3 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jul '19

05 Jul '19

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

1 0

[CQ]: 100024, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 05 Jul '19

05 Jul '19

Change 100024,2 (ovirt-provider-ovn) 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/100024/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14901/

1 0

oVirt infra daily report - unstable production jobs - 876
by jenkins＠jenkins.phx.ovirt.org 05 Jul '19

05 Jul '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/876//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 101366, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jul '19

05 Jul '19

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

1 0

[CQ]: 101365, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jul '19

05 Jul '19

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

1 0

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins
by Germano Veit Michel (oVirt JIRA) 05 Jul '19

05 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2748?page=com.atlassian.jira.… ] Germano Veit Michel edited comment on OVIRT-2748 at 7/4/19 10:29 PM: --------------------------------------------------------------------- [~amarchuk] yes it is, all good. Thank you was (Author: gveitmic): Anton Marchukov yes it is, all good. Thank you > Re: "Dev Role" on Jenkins > ------------------------- > > Key: OVIRT-2748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Dafna Ron > Assignee: Daniel Belenky > > Adding infra-support as this needs a ticket > On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel <germano(a)redhat.com> > wrote: > > Hi, > > > > I would like to be able to manually trigger OST. According to [1] I might > > be missing the "Dev Role" as I cannot see the "*build with parameters*" > > menu. > > > > Could you please check if I have permissions? > > > > [1] > > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/inde… > > > > Thanks, > > Germano > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0