June 2018 - Infra - Ovirt List Archives

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 487 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/487/ Build Number: 487 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #487 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- No tests ran.

6 years, 7 months

1
1
0 / 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2201: -------------------------------- Issue Type: Improvement (was: By-EMAIL) > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu... > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ] Barak Korren updated OVIRT-2201: -------------------------------- Component/s: Standard CI (Pipelines) > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu... > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2201: ------------------------------------- [~sbonazzo(a)redhat.com] rereading our chat transcript above it seems to me that given that in V2, things do not land on 'tested' unless they pass check-merged (in addition to all other conditions), and if we implement OVIRT-1717 (tagging commints that make it to tested), we can drop this requirement. Am I right about this, or are there other use cases I need to take into account? > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu... > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.2 - Build # 296 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.2/296/ Build Number: 296 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #296 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 290 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.... Build Number: 290 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #290 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 485 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/485/ Build Number: 485 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #485 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- No tests ran.

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 247 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-mast... Build Number: 247 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #247 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 265 - Failure!

by jenkins＠jenkins.phx.ovirt.org

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/265/ Build Number: 265 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #265 [Andrej Krejcir] HE: Test restarting HE VM ----------------- 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.

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 38 - Failure!

by jenkins＠jenkins.phx.ovirt.org

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/38/ Build Number: 38 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #38 [Andrej Krejcir] HE: Test restarting HE VM ----------------- Failed Tests: ----------------- All tests passed

6 years, 7 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018