- Infra - oVirt List Archives

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

01 Sep '19

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

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Barak Korren (oVirt JIRA) 01 Sep '19

01 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2566 at 9/1/19 7:52 AM: ------------------------------------------------------------- Not for specific patches - but we can easily enable it for ALL patches. If we only want it for specific patches - we can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits. was (Author: bkorren(a)redhat.com) Not for specific patches - but we can enable it for ALL patches. We can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2566) make network suite blocking
by Barak Korren (oVirt JIRA) 01 Sep '19

01 Sep '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2566: ------------------------------------- Not for specific patches - but we can enable it for ALL patches. We can consider allowing some customization of the Zull configuration at project level to allow running specific suits for specific patches, but this will require some code changes in several places. We can plan this once we're in production with the current set of suits. > make network suite blocking > --------------------------- > > Key: OVIRT-2566 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: danken > Assignee: infra > Priority: High > > The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives. > Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug. > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested". > [~gbenhaim(a)redhat.com] what should be done to make this happen? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

Fwd: Zuul posts non hiddable Gerrit comments
by Barak Korren 01 Sep '19

01 Sep '19

What is out current plan for upgrading to Gerrit 2.15+ ? As you can see below one of the nice features it provides, is the ability to hide auto-generated comments from the UI. This will allow use to de-clutter the comment lists on patches making them easier to track and read. ---------- Forwarded message --------- From: Vitaliy Lotorev <lotorev(a)gmail.com> Date: Fri, 30 Aug 2019 at 01:01 Subject: Zuul posts non hiddable Gerrit comments To: <zuul-discuss(a)lists.zuul-ci.org> Hi, Starting with at least v2.15 Gerrit is able to differentiate bot comments and hide them using 'Show comments' trigger on web UI. This is achived either using tagged comments or robot comments. A while ago I filed an issue about Zuul not using these technics [1] (ticket has links for Gerrit docs with tagged and robot comments). This results that Zuul comments are not hiddable in Gerrit. AFAIK, sending tagged comments via SSH to Gerrit is easy (one-line of code at [2]). I could try providing a patch for tagged comments. What Zuul maintainers think about adding support for bot comments? Should not be sending tagged comments done only if Gerrit version >= 2.15? [1] https://storyboard.openstack.org/#!/story/2005661 [2] https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/gerrit/gerritco… _______________________________________________ Zuul-discuss mailing list Zuul-discuss(a)lists.zuul-ci.org http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 179 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Sep '19

01 Sep '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/179/ Build Number: 179 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #179 [edwardh(a)redhat.com] network, ovirtlib: Expose the root system through sdkentity ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.ha_recovery_43 Error Message: False != True after 600 seconds -------------------- >> begin captured logging << -------------------- lago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2 lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0 lago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output: 7527 lago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0: lago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527 lago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0 --------------------- >> end captured logging << --------------------- Stack Trace: 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.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/004_basic_sanity.py", line 725, in ha_recovery lambda: 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) 'False != True after 600 seconds\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:8157f6f9-b4f5-4fab-a887-59883a5e5d7c:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 875bc492 on lago-compat-4-3-suite-master-host-0: pgrep -f qemu.*guest=vm2\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command 875bc492 on lago-compat-4-3-suite-master-host-0 output:\n 7527\n\nlago.ssh: DEBUG: start task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: end task:2e248e1c-b036-4229-815a-596bfb0cf343:Get ssh client for lago-compat-4-3-suite-master-host-0:\nlago.ssh: DEBUG: Running 87fafbc0 on lago-compat-4-3-suite-master-host-0: kill -KILL 7527\n\nlago.ssh: DEBUG: Command 87fafbc0 on lago-compat-4-3-suite-master-host-0 returned with 0\n--------------------- >> end captured logging << ---------------------'

1 1

oVirt infra daily report - unstable production jobs - 934
by jenkins＠jenkins.phx.ovirt.org 01 Sep '19

01 Sep '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/934//artifact/exported-a… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 933
by jenkins＠jenkins.phx.ovirt.org 31 Aug '19

31 Aug '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/933//artifact/exported-a… Cheers, Jenkins

1 0

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

30 Aug '19

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

1 0

[oVirt] [CQ weekly status] [30-08-2019]
by Dusan Fodor 30 Aug '19

30 Aug '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*: NOT RELEVANT This CQ is not followed anymore, since it's about to be decommissioned. *CQ-4.3*: YELLOW (#1) Last failure was on 28-08 for ovirt-web-ui. It was solved soon after by change 57c5c4b. *CQ-Master:* RED (#1) Last failure was on 30-08 for ovirt-engine in host-deployment. This issue is under investigation. 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-queue-tester/ [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -4.3_change-queue-tester/ [3] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt -master_change-queue-tester/ Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- 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) _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-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/devel@ovirt .org/message/YCNCKRK3G4EJXA3OCYAUS4VMKRDA67F4/

1 0

[CQ]: 102980, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 30 Aug '19

30 Aug '19

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

1 0