May 2018 - Infra - Ovirt List Archives

[CQ]: 90647, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

6 years, 7 months

1
0
0 / 0

[oVirt CI] standard-enqueue - Build #13529 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/13529/ Build Name: #13529 Build Description: Gerrit: 91337 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91337 - title: packaging: setup: postgres95: Pass locale - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Yedidyah Bar David <didi(a)redhat.com>

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 392 - 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/392/ Build Number: 392 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #392 [Sandro Bonazzola] new suite: he-basic-iscsi-suite-4.2 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.add_hosts Error Message: Failed to read response: [(<pycurl.Curl object at 0x7f47f96027f0>, 7, 'TCP connection reset by peer')] -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7f47f957f668> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 253, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36676, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait response = self._connection.wait(self._context) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait return self.__wait(context, failed_auth) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait raise Error("Failed to read response: {}".format(err_list)) Error: Failed to read response: [(<pycurl.Curl object at 0x7f47f96027f0>, 7, 'TCP connection reset by peer')] --------------------- >> 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 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 "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 228, in add_hosts add_hosts_4(prefix) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 275, in add_hosts_4 testlib.assert_true_within(_host_is_up_4, timeout=15*60) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 263, in assert_true_within assert_equals_within(func, True, timeout, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within res = func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 253, in _host_is_up_4 host_obj = host_service.get() File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36676, in get return self._internal_get(headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait response = self._connection.wait(self._context) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait return self.__wait(context, failed_auth) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait raise Error("Failed to read response: {}".format(err_list)) 'Failed to read response: [(<pycurl.Curl object at 0x7f47f96027f0>, 7, \'TCP connection reset by peer\')]\n-------------------- >> begin captured logging << --------------------\novirtlago.testlib: ERROR: * Unhandled exception in <function _host_is_up_4 at 0x7f47f957f668>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n res = func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-master/ovirt-system-tests/hc-basic-suite-master/test-scenarios/002_bootstrap.py", line 253, in _host_is_up_4\n host_obj = host_service.get()\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 36676, in get\n return self._internal_get(headers, query, wait)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 211, in _internal_get\n return future.wait() if wait else future\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 54, in wait\n response = self._connection.wait(self._context)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 496, in wait\n return self.__wait(context, failed_auth)\n File "/usr/lib64/python2.7/site-packages/ovirtsdk4/__init__.py", line 510, in __wait\n raise Error("Failed to read response: {}".format(err_list))\nError: Failed to read response: [(<pycurl.Curl object at 0x7f47f96027f0>, 7, \'TCP connection reset by peer\')]\n--------------------- >> end captured logging << ---------------------'

6 years, 7 months

1
1
0 / 0

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2034: ------------------------------------- One very important concept for implementing the mirrors is creating immutable versions, or snapshots of the content. While this concept is supported by Satellite 6 and probably Katello, according to the document linked below this concept is only supported by Pulp 3 which seems to still be under development: https://docs.pulpproject.org/en/3.0/nightly/overview/from-pulp-2.html > Recreate the transactional CI mirrors with Pulp > ----------------------------------------------- > > Key: OVIRT-2034 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > > Right now, the CI mirrors are created and maintained by a set of custom scripts and jobs. > It seems that [Pulp|https://pulpproject.org/] can do what our current system does. The reason behind not using it when we first made the mirrors system was out desire to provide a quick solution and avoid adding more services to maintain. > There are however, quite a few reasons to want to switch to pulp: > # Aside from RPMs it can also manage other interesting kinds of resources like Containers, DEB packages and Python packages. > # If it works well for us - we can maintain less code by dropping the existing mirror management code > # It has built-in distribution mechanisms that can be useful to scale it up. > # It seems it has support for assigning packages to multiple repos. This cab be used as a tagging mechanism to implement OVIRT-2033 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

[CQ]: 91215,1 (vdsm) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 91215,1 (vdsm) 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/91215/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1956/

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2036: ---------------------------------- Description: Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs hence bypassing our whitelist filtering. We need to fix it by checking if the event matches the actual state of the patch before running any user code. was: Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs. We need to fix it by checking if the event matches the actual state of the patch before running any user code. > Pre-merged patchsets can run on post-merged jobs in STDCI V2 > ------------------------------------------------------------ > > Key: OVIRT-2036 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs hence bypassing our whitelist filtering. > We need to fix it by checking if the event matches the actual state of the patch before running any user code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2037?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2037: ---------------------------------- Epic Link: OVIRT-400 > Patchsets from non-whitelisted users can't run post-merge tasks > --------------------------------------------------------------- > > Key: OVIRT-2037 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2037 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Freestyle) > Reporter: Daniel Belenky > Assignee: infra > > In some cases, even if a patch was created by a non-whitelisted user, project maintainer can decide to merge > the patch. Currently, STDCI (V1) will block the patch from running any post-merge jobs due to whitelist check. > We need to allow project maintainers to bypass the whitelist check or disable whitelist checking on post-merge jobs. > Note: If we decide to disable whitelist check on post-merge jobs, we need to make sure we run post-merge jobs only on *merged* patchsets. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2037) Patchsets from non-whitelisted users can't run post-merge tasks

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2037: ------------------------------------- Summary: Patchsets from non-whitelisted users can't run post-merge tasks Key: OVIRT-2037 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2037 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Freestyle) Reporter: Daniel Belenky Assignee: infra In some cases, even if a patch was created by a non-whitelisted user, project maintainer can decide to merge the patch. Currently, STDCI (V1) will block the patch from running any post-merge jobs due to whitelist check. We need to allow project maintainers to bypass the whitelist check or disable whitelist checking on post-merge jobs. Note: If we decide to disable whitelist check on post-merge jobs, we need to make sure we run post-merge jobs only on *merged* patchsets. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

Tried to build WildFly for FC28

by Martin Perina

Hi, I've tried to rebuild WildFly package for FC28 [1], but the build [2] failed on: *10:37:56* ERROR: Command failed: *10:37:56* # /usr/bin/yum --installroot /var/lib/mock/fedora-28-x86_64-331df456b1f04c7c4dfdcc6461d09745-bootstrap-19748/root/ --releasever 28 install dnf dnf-plugins-core distribution-gpg-keys --setopt=tsflags=nocontexts*10:37:56* Failed to set locale, defaulting to C*10:37:56* http://resources.ovirt.org/repos/ci-tools/fc28/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Do we already support builds for FC28? Thanks Martin [1] https://gerrit.ovirt.org/89197 [2] http://jenkins.ovirt.org/job/ovirt-engine-wildfly_master_build-artifacts-... -- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.

6 years, 7 months

2
4
0 / 0

[JIRA] (OVIRT-2036) Pre-merged patchsets can run on post-merged jobs in STDCI V2

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2036?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-2036: ---------------------------------- Summary: Pre-merged patchsets can run on post-merged jobs in STDCI V2 (was: Post merge patchsets can run on pre-merge jobs in STDCI V2) > Pre-merged patchsets can run on post-merged jobs in STDCI V2 > ------------------------------------------------------------ > > Key: OVIRT-2036 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2036 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Currently, if one comments 'ci re-merge please' on a pre-merged patch, STDCI V2 will run post-merge jobs. > We need to fix it by checking if the event matches the actual state of the patch before running any user code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2018