July 2018 - Infra - oVirt List Archives

[CQ]: 93178,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 22 Jul '18

22 Jul '18

Change 93178,2 (ovirt-engine) 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://gerrit.ovirt.org/#/c/93178/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2690/

3 2

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Barak Korren (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2359: ------------------------------------- I say jenkins should have nothing to do with this, it should be set by the script that starts up the containers. > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Eyal Edri (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2358?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2358: ---------------------------------- Can you please explain why do you need to keep forever builds? for which project and what is the goal? All of the artifacts you build in Jenkins usually go to resources.ovirt.org and kept there for at least one month. > Permissions to revert "keep build forever" in jenkins > ----------------------------------------------------- > > Key: OVIRT-2358 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I seem to be missing permission to revert "keep build forever" in jenkins. > Can you add me this permission? > Thanks, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2359: ---------------------------------- Epic Link: OVIRT-2326 > Set environment variable in jenkins user's env to inidicate it's a container > ---------------------------------------------------------------------------- > > Key: OVIRT-2359 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 22 Jul '18

22 Jul '18

Daniel Belenky created OVIRT-2359: ------------------------------------- Summary: Set environment variable in jenkins user's env to inidicate it's a container Key: OVIRT-2359 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2358) Permissions to revert "keep build forever" in jenkins
by Shirly Radco (oVirt JIRA) 22 Jul '18

22 Jul '18

Shirly Radco created OVIRT-2358: ----------------------------------- Summary: Permissions to revert "keep build forever" in jenkins Key: OVIRT-2358 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2358 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Shirly Radco Assignee: infra Hi, I seem to be missing permission to revert "keep build forever" in jenkins. Can you add me this permission? Thanks, -- SHIRLY RADCO BI SENIOR SOFTWARE ENGINEER Red Hat Israel <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-fc28-x86_64 - Build # 4 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build Number: 4 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #4 [Yuval Turgeman] automation: remove build-artifacts* from stdci-v2 ----------------- Failed Tests: ----------------- No tests ran.

1 1

Re: Change in ovirt-engine[master]: packaging: setup: postgres95: Verify selinux file contexts
by Yedidyah Bar David 22 Jul '18

22 Jul '18

On Thu, Jul 19, 2018 at 12:47 PM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. > > Change subject: packaging: setup: postgres95: Verify selinux file contexts > ...................................................................... > > > Patch Set 4: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc28-x86_64/12… : FAILURE This failed (more than ones, but not always, for now) with: 09:13:11 No match for argument: otopi 09:13:11 Error: Unable to find a match Not sure if that's related, but since some weeks ago, we no longer have in master a package called 'otopi'. Instead, a new package 'python2-otopi' should provide otopi. Any idea? Thanks. > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/417… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/93147 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: Ic12c5252d1f7597b1ab5ff012b195ed04addbe48 > Gerrit-Change-Number: 93147 > Gerrit-PatchSet: 4 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > Gerrit-Reviewer: Ido Rosenzwig <irosenzw(a)redhat.com> > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-Comment-Date: Thu, 19 Jul 2018 09:47:40 +0000 > Gerrit-HasComments: No -- Didi

2 3

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 145 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/14… Build Number: 145 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #145 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- All tests passed

1 2

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 371 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Jul '18

22 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/371/ Build Number: 371 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #371 [Milan Zamazal] Fix reported test names ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 409 reason: Conflict detail: Cannot create Snapshot. Snapshot is currently being created for VM vm0. 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 129, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 194, in snapshot_merge api.vms.get(VM0_NAME).snapshots.add(dead_snap2_params) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34511, in add headers={"Correlation-Id":correlation_id, "Expect":expect} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add return self.request('POST', url, body, headers, cls=cls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request persistent_auth=self.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body) RequestError: status: 409 reason: Conflict detail: Cannot create Snapshot. Snapshot is currently being created for VM vm0.

1 2