June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2135) On failure we collect the logs from the VMs twice

by Gal Ben Haim (oVirt JIRA)

Gal Ben Haim created OVIRT-2135: ----------------------------------- Summary: On failure we collect the logs from the VMs twice Key: OVIRT-2135 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2135 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra The first collection is done by `LogCollector` nose plugin (this plugin is defined in ovirtlago.testlib) The second collection is done by `env_collect` in the `control.sh` script of the suite. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-master" system tests

by oVirt Jenkins

Change 82632,1 (py2exe-py2.7) 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/82632/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8046/

6 years, 7 months

1
0
0 / 0

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-4.2" system tests

by oVirt Jenkins

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

6 years, 7 months

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1550

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1550/dis...> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 5cb82835887b96781c1ec5514c0309078f60d3f2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5cb82835887b96781c1ec5514c0309078f60d3f2 Commit message: "cockpit-ovirt: Move to fc28 and exclude 4.2 on fc28" > git rev-list --no-walk 5cb82835887b96781c1ec5514c0309078f60d3f2 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins879410915074091692.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

6 years, 7 months

1
1
0 / 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jir... ] sbonazzo commented on OVIRT-2078: --------------------------------- Note that https://gerrit-review.googlesource.com/Documentation/intro-user.html#priv... says also: bq. "For CI systems that must verify private changes, a special permission can be granted (View Private Changes). In that case, care should be taken to prevent the CI system from exposing secret details." so we should research also for a jenkins plugin which allows to test such private change without exposing it. > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#priv... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jir... ] sbonazzo commented on OVIRT-2078: --------------------------------- User story: A researcher find a vulnerability in one of the oVirt packages. A CVE is opened and an embargo date is acknowledged between researcher, oVirt package maintainer and downstream vendors. Between report and embargo date, oVirt package maintainer must be able to push a patch to gerrit as a private patch, getting it reviewed by a restricted number of people and get it ready for being merged immediately on embargo lift, when the vulnerability will be disclosed to public, in order to issue an immediate release right after the merge. > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#priv... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2074) missing dependency for python-isort

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2074?page=com.atlassian.jir... ] sbonazzo reassigned OVIRT-2074: ------------------------------- Assignee: sbonazzo (was: infra) > missing dependency for python-isort > ----------------------------------- > > Key: OVIRT-2074 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2074 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: sbonazzo > Labels: cq-issue-traking, ost_failures > > need to change fc27 to fc28 to fix the failures. > Sandro submitted a change for some projects but some are still missing. > Sandro: > Fix is here: https://gerrit.ovirt.org/91769 ; needs an engine to be built on fedora to pass CI, I'm on it. > Going on failures, I will help him with the change for failed projects build-artifacts with the same issue. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[CQ]: 91378, 3 (ovirt-engine) 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 91378,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91888,3 (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 91888,3 (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/91378/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91888/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8041/

6 years, 7 months

1
0
0 / 0

[CQ]: 91841, 7 (ovirt-engine) 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 91841,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91888,3 (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 91888,3 (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/91841/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91888/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8037/

6 years, 7 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 228 - 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/228/ Build Number: 228 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #228 [Milan Zamazal] Use Cirros 0.4.0 for cluster versions < 4.1 [Yuval Turgeman] system-tests: added he-node-ng-master suite [Barak Korren] Fix mock_cleanup.sh trying to umount bad things [Barak Korren] Switch fabric-ovirt to STDCI v2 ----------------- Failed Tests: ----------------- No tests ran.

6 years, 7 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018