May 2018 - Infra - oVirt List Archives

[CQ]: 91359, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

2 1

[CQ]: 90625, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

2 1

[CQ]: 91661, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

2 1

[JIRA] (OVIRT-2060) ovirt-engine master regression in disk_operations in basic_suit
by Barak Korren (oVirt JIRA) 28 May '18

28 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2060?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2060: ----------------------------------- Assignee: Barak Korren (was: infra) > ovirt-engine master regression in disk_operations in basic_suit > --------------------------------------------------------------- > > Key: OVIRT-2060 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2060 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > Labels: cq-issue-traking > > There seems to be a new ovirt-engine master branch regression that is causing the [004_basic_sanity.disk_operations|http://jenkins.ovirt.org/job/ovirt-master_…] test of the basic_suit to fail. > Issue first detected in the following patch: > https://gerrit.ovirt.org/#/c/91068/4 > First failing test: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/ > Since this regression is occurring in parallel to the one tracked in OVIRT-2059, CQ RCA analysis points to the patch that caused OVIRT-2059. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91068, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 May '18

28 May '18

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

2 1

[JIRA] (OVIRT-2060) ovirt-engine master regression in disk_operations in basic_suit
by Barak Korren (oVirt JIRA) 28 May '18

28 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2060?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2060: -------------------------------- Epic Link: OVIRT-400 > ovirt-engine master regression in disk_operations in basic_suit > --------------------------------------------------------------- > > Key: OVIRT-2060 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2060 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: cq-issue-traking > > There seems to be a new ovirt-engine master branch regression that is causing the [004_basic_sanity.disk_operations|http://jenkins.ovirt.org/job/ovirt-master_…] test of the basic_suit to fail. > Issue first detected in the following patch: > https://gerrit.ovirt.org/#/c/91068/4 > First failing test: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/ > Since this regression is occurring in parallel to the one tracked in OVIRT-2059, CQ RCA analysis points to the patch that caused OVIRT-2059. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2060) ovirt-engine master regression in disk_operations in basic_suit
by Barak Korren (oVirt JIRA) 28 May '18

28 May '18

Barak Korren created OVIRT-2060: ----------------------------------- Summary: ovirt-engine master regression in disk_operations in basic_suit Key: OVIRT-2060 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2060 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI client projects Reporter: Barak Korren Assignee: infra Priority: Highest There seems to be a new ovirt-engine master branch regression that is causing the [004_basic_sanity.disk_operations|http://jenkins.ovirt.org/job/ovirt-master_…] test of the basic_suit to fail. Issue first detected in the following patch: https://gerrit.ovirt.org/#/c/91068/4 First failing test: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7811/ Since this regression is occurring in parallel to the one tracked in OVIRT-2059, CQ RCA analysis points to the patch that caused OVIRT-2059. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1524
by jenkins＠jenkins.phx.ovirt.org 27 May '18

27 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1524/displ…> Changes: [Daniel Belenky] Add git variables to standard enqueue ------------------------------------------ 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 71f25ef8ea8e1e2026ab43982d8eacca30f4b7cb (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 71f25ef8ea8e1e2026ab43982d8eacca30f4b7cb Commit message: "Add git variables to standard enqueue" > git rev-list --no-walk 65d5fbb25c89357a83bc940bc9b060f46d7bd93a # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins2534436610042358014.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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1452, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-updates-fc26/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

[CQ]: 91473, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 May '18

27 May '18

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

1 0

Change in us-jenkins-stg2[master]: Revert "asdf"
by review＠gerrit-staging.phx.ovirt.org 27 May '18

27 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Hello Jenkins CI, I'd like you to do a code review. Please visit https://gerrit-staging.phx.ovirt.org/160 to review the following change. Change subject: Revert "asdf" ...................................................................... Revert "asdf" This reverts commit e5adda75aebb8cfb19e0ec50d628620b5ab73730. Change-Id: I871a394592ae4eed5aba887bb167052aec5ef49b --- M upstream-file1.txt 1 file changed, 0 insertions(+), 1 deletion(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/us-jenkins-stg2 refs/changes/60/160/1 -- To view, visit https://gerrit-staging.phx.ovirt.org/160 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: I871a394592ae4eed5aba887bb167052aec5ef49b Gerrit-Change-Number: 160 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 3