- Infra - oVirt List Archives

[CQ]: 1161726 (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-master" change queue including change 1161726 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/1161726147b28179abe16f2… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13412/

1 0

[CQ]: a9bd6c5 (v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 14 Mar '19

14 Mar '19

Change a9bd6c5 (v2v-conversion-host) 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/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13409/

1 0

[CQ]: bfb10eb (v2v-conversion-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change bfb10eb (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/bfb10eb183fcb76cac50d89… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/225/

1 0

[CQ]: bfb10eb (v2v-conversion-host) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-4.2" change queue including change bfb10eb (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/bfb10eb183fcb76cac50d89… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4058/

1 0

[CQ]: 8d09024 (v2v-conversion-host) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-4.2" change queue including change 8d09024 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/8d090241ee30a30e05023a5… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4056/

1 0

[CQ]: 8d09024 (v2v-conversion-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change 8d09024 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/8d090241ee30a30e05023a5… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/223/

1 0

[CQ]: 1161726 (v2v-conversion-host) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-4.2" change queue including change 1161726 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/1161726147b28179abe16f2… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4054/

1 0

[CQ]: 1161726 (v2v-conversion-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Mar '19

14 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change 1161726 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change a9bd6c5 (v2v-conversion-host) 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 a9bd6c5 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/1161726147b28179abe16f2… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/221/

1 0

[CQ]: a9bd6c5 (v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Mar '19

14 Mar '19

Change a9bd6c5 (v2v-conversion-host) 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/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4053/

1 0

[CQ]: a9bd6c5 (v2v-conversion-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 14 Mar '19

14 Mar '19

Change a9bd6c5 (v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/v2v-conversion-host/commit/a9bd6c54d63bc66a03ec558… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/219/

1 0

oVirt infra daily report - unstable production jobs - 763
by jenkins＠jenkins.phx.ovirt.org 14 Mar '19

14 Mar '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/763//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 98515,2 (ovirt-guest-agent) failed "ovirt-master" system tests
by oVirt Jenkins 13 Mar '19

13 Mar '19

Change 98515,2 (ovirt-guest-agent) 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/98515/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13403/

1 0

[CQ]: a1bcd88 (v2v-conversion-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 13 Mar '19

13 Mar '19

Change a1bcd88 (v2v-conversion-host) 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/v2v-conversion-host/commit/a1bcd889ee558febed3d6df… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4048/

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Dafna Ron (oVirt JIRA) 13 Mar '19

13 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2697: ---------------------------------- [~akhiet(a)redhat.com] Eyal is correct that your patch failed on a test from ost. you can see the test it failed on at the bottom of this page: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4302/ The error is captured by lago usually so if you select the link you can see the error is: {noformat} 'could not locate by id: compute' -------------------- >> begin captured stdout << --------------------- could not locate by id: compute hover_to_id couldnt find element compute However, you can look at the full logs here: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4302/artifact/expor… If you do not think that the error is related to your change (I am not sure which one its is as its not in the job) you can try to re-run it to see if this was a race which failed that specific test. {noformat} > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Ahmad Khiet (oVirt JIRA) 13 Mar '19

13 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Ahmad Khiet commented on OVIRT-2697: ------------------------------------ [~dron] can you take a look? > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Eyal Edri (oVirt JIRA) 13 Mar '19

13 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2697: ---------------------------------- You need to look at the junit test results to understand the error ( which is in the test, so probably related to your code ): https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4302/testReport/jun… On Wed, Mar 13, 2019 at 12:00 PM Ahmad Khiet (oVirt JIRA) < -- Eyal edri MANAGER RHV/CNV 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) > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Ahmad Khiet (oVirt JIRA) 13 Mar '19

13 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Ahmad Khiet commented on OVIRT-2697: ------------------------------------ rebased the code and still getting errors: 11:35:23 ~ [Thread-4] Copy from lago-basic-suite-master-engine:/tmp/otopi* to /dev/shm/ost/deployment-basic-suite-master/default/test_logs/008_basic_ui_sanity.left_nav-20190313093523/lago-basic-suite-master-engine/_tmp_otopi*: ERROR (in 0:00:00) 11:35:23 - [Thread-4] lago-basic-suite-master-engine: ERROR (in 0:00:00) 11:35:25 * Collect artifacts: ERROR (in 0:00:02) 11:35:25 # left_nav: ERROR (in 0:00:31) 11:35:25 # Results located at /dev/shm/ost/deployment-basic-suite-master/008_basic_ui_sanity.py.junit.xml 11:35:25 @ Run test: 008_basic_ui_sanity.py: ERROR (in 0:03:10) 11:35:25 Error occured, aborting 11:35:25 Traceback (most recent call last): 11:35:25 File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 383, in do_run 11:35:25 self.cli_plugins[args.ovirtverb].do_run(args) 11:35:25 File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 184, in do_run 11:35:25 self._do_run(**vars(args)) 11:35:25 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 549, in wrapper 11:35:25 return func(*args, **kwargs) 11:35:25 File "/usr/lib/python2.7/site-packages/lago/utils.py", line 560, in wrapper 11:35:25 return func(*args, prefix=prefix, **kwargs) 11:35:25 File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 107, in do_ovirt_runtest 11:35:25 raise RuntimeError('Some tests failed') 11:35:25 RuntimeError: Some tests failed 11:35:25 + res=1 https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4302/consoleFull > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

2 1

[CQ]: 98417,10 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 13 Mar '19

13 Mar '19

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

1 0

oVirt infra daily report - unstable production jobs - 762
by jenkins＠jenkins.phx.ovirt.org 13 Mar '19

13 Mar '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/762//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 98416, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '19

12 Mar '19

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

1 0

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

12 Mar '19

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

1 0

[CQ]: 98387, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Mar '19

12 Mar '19

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

1 0

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

12 Mar '19

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

1 0

[JIRA] (OVIRT-2701) 'dev' role for Jenkins is required
by Eyal Edri (oVirt JIRA) 12 Mar '19

12 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2701?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2701: ---------------------------------- I resent the invite, but the access to Jenkins should be given on Jenkins server. [~amarchuk] who can help here? > 'dev' role for Jenkins is required > ---------------------------------- > > Key: OVIRT-2701 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2701 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Bar > Assignee: infra > Attachments: image.png > > > Hi, > Can you please add me the 'dev' role for Jenkins? > So I'll be able to trigger build on Jenkins. > Thank you in advance! > Pavel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2701) 'dev' role for Jenkins is required
by Pavel Bar (oVirt JIRA) 12 Mar '19

12 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2701?page=com.atlassian.jira.… ] Pavel Bar updated OVIRT-2701: ----------------------------- Attachment: image.png Hi, I received the "Jura account created" email, but now can't reset my password: [image: image.png] Is it something that you may help? Thank you in advance! Pavel On Tue, Mar 12, 2019 at 1:58 PM Pavel Bar <pbar(a)redhat.com> wrote: > Hi, > Can you please add me the 'dev' role for Jenkins? > So I'll be able to trigger build on Jenkins. > > Thank you in advance! > > Pavel > > > 'dev' role for Jenkins is required > ---------------------------------- > > Key: OVIRT-2701 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2701 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Bar > Assignee: infra > Attachments: image.png > > > Hi, > Can you please add me the 'dev' role for Jenkins? > So I'll be able to trigger build on Jenkins. > Thank you in advance! > Pavel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2701) 'dev' role for Jenkins is required
by Pavel Bar (oVirt JIRA) 12 Mar '19

12 Mar '19

Pavel Bar created OVIRT-2701: -------------------------------- Summary: 'dev' role for Jenkins is required Key: OVIRT-2701 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2701 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Pavel Bar Assignee: infra Hi, Can you please add me the 'dev' role for Jenkins? So I'll be able to trigger build on Jenkins. Thank you in advance! Pavel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2700) Fwd: Jenkins permissions
by Anton Marchukov (oVirt JIRA) 12 Mar '19

12 Mar '19

Anton Marchukov created OVIRT-2700: -------------------------------------- Summary: Fwd: Jenkins permissions Key: OVIRT-2700 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2700 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Adding infra-support to open the ticket. > Begin forwarded message: > > From: Bell Levin <blevin(a)redhat.com> > Subject: Jenkins permissions > Date: 12 March 2019 at 12:54:27 CET > To: infra(a)ovirt.org > > Hey, > I would like to get permissions to run builds on Jenkins. Currently i do not have build and manual run permissions. > > Please let me know if you need any additional information. > > Thanks, > Bell > _______________________________________________ > 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/K36ZSTUSKHECD… -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2699) proxy01.phx.ovirt.org:3128 can't be reached from Jenkins slaves
by Anton Marchukov (oVirt JIRA) 12 Mar '19

12 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2699?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2699: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > proxy01.phx.ovirt.org:3128 can't be reached from Jenkins slaves > --------------------------------------------------------------- > > Key: OVIRT-2699 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2699 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Jenkins jobs are issuing warning like: > Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to > non-proxied config > Example: > https://jenkins.ovirt.org/job/ovirt-lldp-labeler_standard-check-patch/18/co… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

Jenkins permissions
by Bell Levin 12 Mar '19

12 Mar '19

Hey, I would like to get permissions to run builds on Jenkins. Currently i do not have build and manual run permissions. Please let me know if you need any additional information. Thanks, Bell

1 0

Change in stdci-sample-liora[master]: onboard standard ci
by review＠gerrit-staging.phx.ovirt.org 12 Mar '19

12 Mar '19

From Liora Milbaum <lmilbaum(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/225 to look at the new patch set (#3). Change subject: onboard standard ci ...................................................................... onboard standard ci Change-Id: If2e461c8b8954708476f4d6954e9813729b9c997 --- A automation/check-patch.sh A stdci.yaml 2 files changed, 14 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stdci-sample-liora refs/changes/25/225/3 -- To view, visit https://gerrit-staging.phx.ovirt.org/225 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-sample-liora Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: If2e461c8b8954708476f4d6954e9813729b9c997 Gerrit-Change-Number: 225 Gerrit-PatchSet: 3 Gerrit-Owner: Liora Milbaum <lmilbaum(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in stdci-sample-liora[master]: onboard standard ci
by review＠gerrit-staging.phx.ovirt.org 12 Mar '19

12 Mar '19

From Liora Milbaum <lmilbaum(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/225 to look at the new patch set (#2). Change subject: onboard standard ci ...................................................................... onboard standard ci Change-Id: If2e461c8b8954708476f4d6954e9813729b9c997 --- A stdci.yaml 1 file changed, 9 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stdci-sample-liora refs/changes/25/225/2 -- To view, visit https://gerrit-staging.phx.ovirt.org/225 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-sample-liora Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: If2e461c8b8954708476f4d6954e9813729b9c997 Gerrit-Change-Number: 225 Gerrit-PatchSet: 2 Gerrit-Owner: Liora Milbaum <lmilbaum(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt-ansible_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Mar '19

12 Mar '19

Failed to run project_setup.sh for: #2524 kubevirt-ansible [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 ovirt-srv18.phx.ovirt.org.

1 0

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

12 Mar '19

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

1 0

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

12 Mar '19

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

1 0

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

12 Mar '19

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

1 0

[CQ]: 98465, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 12 Mar '19

12 Mar '19

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

1 0

oVirt infra daily report - unstable production jobs - 761
by jenkins＠jenkins.phx.ovirt.org 12 Mar '19

12 Mar '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/761//artifact/exported-a… Cheers, Jenkins

1 0

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

11 Mar '19

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

1 0

[CQ]: 1fdac3f (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Mar '19

11 Mar '19

Change 1fdac3f (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.3" 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-hosted-engine-setup/commit/1fdac3fac… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/195/

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Dafna Ron (oVirt JIRA) 11 Mar '19

11 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2697: ---------------------------------- the job is running from your build-artifacts packages and its failing in missing packages (see below). after reviewing the packages available in CI repos, the deps you are trying to get are outdated as we now work with postgresql10 and some are no longer needed. I suggest that you rebaseyour change and build new packages {noformat} 12:16:21 + install_cmd='yum install --nogpgcheck --downloaddir=/dev/shm -y' 12:16:21 + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie 12:16:21 Error: Package: ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rubygem-fluent-plugin-collectd-nest 12:16:21 Error: Package: ovirt-engine-tools-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: gdeploy 12:16:21 Error: Package: ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rh-postgresql95-postgresql-server 12:16:21 Error: Package: ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rh-postgresql95-postgresql-contrib 12:16:21 Error: Package: ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rubygem-fluent-plugin-secure-forward 12:16:21 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rh-postgresql95-postgresql-server 12:16:21 Error: Package: ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rubygem-fluent-plugin-rewrite-tag-filter 12:16:21 Error: Package: ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rubygem-fluent-plugin-viaq_data_model 12:16:21 Error: Package: ovirt-engine-tools-backup-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rh-postgresql95-postgresql 12:16:21 Error: Package: ovirt-engine-setup-plugin-ovirt-engine-4.3.0-0.2.master.20190310093054.git6f320b3.el7.noarch (alocalsync) 12:16:21 Requires: rh-postgresql95-postgresql-contrib 12:16:21 + ret=1 {noformat} current packages includepkgs = rh-postgresql10-postgresql rh-postgresql10-postgresql-contrib rh-postgresql10-postgresql-libs rh-postgresql10-postgresql-server rh-postgresql10-runtime > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2699) proxy01.phx.ovirt.org:3128 can't be reached from Jenkins slaves
by sbonazzo (oVirt JIRA) 11 Mar '19

11 Mar '19

sbonazzo created OVIRT-2699: ------------------------------- Summary: proxy01.phx.ovirt.org:3128 can't be reached from Jenkins slaves Key: OVIRT-2699 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2699 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Jenkins jobs are issuing warning like: Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config Example: https://jenkins.ovirt.org/job/ovirt-lldp-labeler_standard-check-patch/18/co… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Ahmad Khiet (oVirt JIRA) 11 Mar '19

11 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Ahmad Khiet commented on OVIRT-2697: ------------------------------------ tried, I'm still getting errors: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4278/console > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98351,1 (vdsm-jsonrpc-java) failed "ovirt-4.3" system tests
by oVirt Jenkins 11 Mar '19

11 Mar '19

Change 98351,1 (vdsm-jsonrpc-java) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/98351/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/189/

2 1

[CQ]: 9fbdbc1 (ovirt-ansible-vm-infra) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Mar '19

11 Mar '19

Change 9fbdbc1 (ovirt-ansible-vm-infra) 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-vm-infra/commit/9fbdbc1add5c0c194b06… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4029/

1 0

[JIRA] (OVIRT-2697) error before starting tests
by Dafna Ron (oVirt JIRA) 11 Mar '19

11 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2697?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2697: ---------------------------------- we had missing packages last week due to a missing repo. please try to re-run the job > error before starting tests > --------------------------- > > Key: OVIRT-2697 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2697 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Ahmad Khiet > Assignee: infra > Priority: High > Labels: ost_failures > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2696) verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status'
by Dafna Ron (oVirt JIRA) 11 Mar '19

11 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2696: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status' > ---------------------------------------------------------------------------------- > > Key: OVIRT-2696 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Priority: High > Labels: ost_failures > > [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > Project name - ovirt-engine > Branch - ovirt-master > Failed Suite - basic suite > Failed test/failed phase > Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ > Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2696) verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status'
by Dafna Ron (oVirt JIRA) 11 Mar '19

11 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2696?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2696: ---------------------------------- this was already resolved: https://gerrit.ovirt.org/#/c/98317/ > verify_glance_import - AttributeError: 'NoneType' object has no attribute 'status' > ---------------------------------------------------------------------------------- > > Key: OVIRT-2696 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2696 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Liora Milbaum > Assignee: infra > Priority: High > Labels: ost_failures > > [CQ]: 98221, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause > Project name - ovirt-engine > Branch - ovirt-master > Failed Suite - basic suite > Failed test/failed phase > Link to first reported failed build - http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13306/ > Link to first reported failed patch - https://gerrit.ovirt.org/#/c/97965/5 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 08-03-2019 ] [ 002_bootstrap.verify_add_hosts ]
by Dafna Ron 11 Mar '19

11 Mar '19

Hi, We are failing vdsm project on master branch with test 002_bootstrap.verify_add_hosts CQ identified this patch as the root cause: https://gerrit.ovirt.org/#/c/97381/ - virt: In FIPS mode, use SASL auth instead of qemu passwords Can you please take a look? build logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13317/artifa… <error> host: 2019-03-07 17:37:38,839-0500 ERROR (MainThread) [vds] Exception raised (vdsmd:159) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 157, in run serve_clients(log) File "/usr/lib/python2.7/site-packages/vdsm/vdsmd.py", line 103, in serve_clients from vdsm.clientIF import clientIF # must import after config is read File "/usr/lib/python2.7/site-packages/vdsm/clientIF.py", line 64, in <module> from vdsm.virt import vm File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 81, in <module> from vdsm.virt import saslpasswd2 ImportError: cannot import name saslpasswd2 2019-03-07 17:37:38,841-0500 INFO (MainThread) [vds] Stopping threads (vdsmd:161) 2019-03-07 17:37:38,841-0500 INFO (MainThread) [vds] Stopping <MonitorObserver(mpathlistener, started daemon 139815311881984)> (vdsmd:164) engine: 2019-03-07 17:37:47,780-05 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [] Command 'G etCapabilitiesAsyncVDSCommand(HostName = lago-basic-suite-master-host-1, VdsIdAndVdsVDSCommandParametersBase:{hostId='5d685bce-ada7-4730-975c-45d30afc0a8b', vds='Host[lago-b asic-suite-master-host-1,5d685bce-ada7-4730-975c-45d30afc0a8b]'})' execution failed: java.net.ConnectException: Connection refused 2019-03-07 17:37:47,780-05 DEBUG [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-28) [] Exception: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: java.net.ConnectException: Connection refused at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.createNetworkException(VdsBrokerCommand.java:172) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVdsCommandWithNetworkEvent(VdsBrokerCommand.java:135) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerCommand.executeVDSCommand(VdsBrokerCommand.java:111) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VDSCommandBase.executeCommand(VDSCommandBase.java:65) [vdsbroker.jar:] at org.ovirt.engine.core.dal.VdcCommandBase.execute(VdcCommandBase.java:31) [dal.jar:] at org.ovirt.engine.core.vdsbroker.vdsbroker.DefaultVdsCommandExecutor.execute(DefaultVdsCommandExecutor.java:14) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager.runVdsCommand(ResourceManager.java:396) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source) [:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.5.Final. jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.GeneratedMethodAccessor61.invoke(Unknown Source) [:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.5.Final.jar:3 .0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-3.0. 5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-3.0. 5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.runVdsCommand(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.VdsManager.refreshCapabilities(VdsManager.java:779) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring.refreshCapabilities(HostMonitoring.java:189) [vdsbroker.jar:] </error>

2 8

otopi: release branches and change queues
by Yedidyah Bar David 11 Mar '19

11 Mar '19

Hi all, I branched yesterday otopi-1.8 to be used for ovirt-4.3, and forgot to patch stdci accordingly. Now pushed the patch [1] (to both master and otopi-1.8 - I realize I do not need it in master, but hopefully this will help me remember patching it in 4.4). What can/should I do to include the otopi-1.8.1 build [2] in the 4.3 change queue? And, related to this, some ideas about how to make stdci more useful for mere developers: 1. Make the change-queue post comments in gerrit patches once it has a result (patch passed change queue X, failed, something else?). I (as always) prefer a bit more information (e.g. a few more comments that might not be that interesting) than not enough (current). We can always refine later. IIRC this was already discussed in the past - any update? 2. Make the current comment "This change was successfully submitted to the change queue(s) for system testing." more informative - include names of change queues and links to relevant pages (builds? not sure, I do not know enough CI). 3. As a side note, I realize that the option names were made case-insensitive and ignore whitespace/dashes/underscores in order to not impose a certain style on the many different projects/maintainers and let them use what they find best for their project. I personally think this was a mistake. If you have to make a choice when naming something, and have a feeling that your opinion might cause noise/objections/etc. in the future, make a quick poll asking what people prefer, and then pick a single name. Having several (many) different names for things makes it much harder later on to _find_ them. It might be too late now to change, because people might already picked different names in practice and we do not want to break their stuff, and that's a pity. But next time, be opinionated, or ask beforehand - not keep the choice. Most computer languages and libraries have single unique names for things, for a reason. [1] https://gerrit.ovirt.org/#/q/I794426ec9212e0a023c3e5f158d0a88fc8e6842c [2] https://gerrit.ovirt.org/98408 -- Didi

2 2

oVirt infra daily report - unstable production jobs - 760
by jenkins＠jenkins.phx.ovirt.org 11 Mar '19

11 Mar '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/760//artifact/exported-a… Cheers, Jenkins

1 0