- 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

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el7-x86_64 - Build # 353 - Failure!
by jenkins＠jenkins.phx.ovirt.org 27 May '18

27 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2-pre_build-artifacts-el… Build Number: 353 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #353 [Sandro Bonazzola] kickstart: drop upstream cockpit copr repo ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

27 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/157 ) Change subject: asdf ...................................................................... asdf Change-Id: I3240e6399d7cf522150a5cd37c74bf09a4ffa290 Signed-off-by: Daniel Belenky <dbelenky(a)redhat.com> --- M upstream-file1.txt 1 file changed, 1 insertion(+), 0 deletions(-) Approvals: Jenkins CI: Passed CI tests Daniel Belenky: Looks good to me, approved; Verified -- To view, visit https://gerrit-staging.phx.ovirt.org/157 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: merged Gerrit-Change-Id: I3240e6399d7cf522150a5cd37c74bf09a4ffa290 Gerrit-Change-Number: 157 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

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

27 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/157 ) Change subject: asdf ...................................................................... Patch Set 1: Verified+1 Code-Review+2 -- To view, visit https://gerrit-staging.phx.ovirt.org/157 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: us-jenkins-stg2 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I3240e6399d7cf522150a5cd37c74bf09a4ffa290 Gerrit-Change-Number: 157 Gerrit-PatchSet: 1 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Sun, 27 May 2018 08:36:33 +0000 Gerrit-HasComments: No

1 0

[CQ]: 91524, 2 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 27 May '18

27 May '18

Change 91524,2 (ovirt-provider-ovn) 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/91524/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7789/

2 1

[CQ]: 91630, 1 (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 91630,1 (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/91630/1 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/7802/

2 1

[CQ]: 91505, 2 (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 91505,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/91505/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/7793/

2 1

[CQ]: 91462, 7 (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 91462,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/91462/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/7786/

2 1

[CQ]: 91576, 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 91576,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/91576/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/7782/

2 1

[CQ]: 91445,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 27 May '18

27 May '18

Change 91445,5 (ovirt-engine) 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/91445/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7776/

2 1

[JIRA] (OVIRT-2059) ovirt-engine master regresssion in post-upgrade Addhost for upgrade-from-release-suite
by Barak Korren (oVirt JIRA) 27 May '18

27 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2059?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2059: ----------------------------------- Assignee: Barak Korren (was: infra) > ovirt-engine master regresssion in post-upgrade Addhost for upgrade-from-release-suite > --------------------------------------------------------------------------------------- > > Key: OVIRT-2059 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2059 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > > There seems to be a new regression in the ovirt-engine master branch. > The regression was first reported on the following patch: > https://gerrit.ovirt.org/#/c/91445/5 > It has since have affected multiple other engine patches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2059) ovirt-engine master regresssion in post-upgrade Addhost for upgrade-from-release-suite
by Barak Korren (oVirt JIRA) 27 May '18

27 May '18

Barak Korren created OVIRT-2059: ----------------------------------- Summary: ovirt-engine master regresssion in post-upgrade Addhost for upgrade-from-release-suite Key: OVIRT-2059 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2059 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 regression in the ovirt-engine master branch. The regression was first reported on the following patch: https://gerrit.ovirt.org/#/c/91445/5 It has since have affected multiple other engine patches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2059) ovirt-engine master regresssion in post-upgrade Addhost for upgrade-from-release-suite
by Barak Korren (oVirt JIRA) 27 May '18

27 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2059?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2059: -------------------------------- Epic Link: OVIRT-400 > ovirt-engine master regresssion in post-upgrade Addhost for upgrade-from-release-suite > --------------------------------------------------------------------------------------- > > Key: OVIRT-2059 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2059 > 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 regression in the ovirt-engine master branch. > The regression was first reported on the following patch: > https://gerrit.ovirt.org/#/c/91445/5 > It has since have affected multiple other engine patches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2058) rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade
by Douglas Landgraf (oVirt JIRA) 27 May '18

27 May '18

Douglas Landgraf created OVIRT-2058: --------------------------------------- Summary: rename project: ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade Key: OVIRT-2058 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2058 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Douglas Landgraf Assignee: infra Hi, Please rename project ovirt-engine-hyper-upgrade to rhvm-fast-forward-upgrade in gerrit and related components. Reason: project name consistency Thanks! -- Cheers Douglas -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

2 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1600
by jenkins＠jenkins.phx.ovirt.org 27 May '18

27 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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-centos-updates-el7-x86_64/…> > 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 65d5fbb25c89357a83bc940bc9b060f46d7bd93a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 65d5fbb25c89357a83bc940bc9b060f46d7bd93a Commit message: "drop EOL 4.1 appliance builds and jobs" > git rev-list --no-walk 65d5fbb25c89357a83bc940bc9b060f46d7bd93a # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4649909027337205596.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 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

1 1

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

26 May '18

A system test invoked by the "ovirt-master" change queue including change 91522,9 (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/91522/9 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/7805/

1 0

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

26 May '18

A system test invoked by the "ovirt-master" change queue including change 91471,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/91471/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/7800/

1 0

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

26 May '18

A system test invoked by the "ovirt-master" change queue including change 91615,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/91615/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/7797/

1 0

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

26 May '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1518/displ…> ------------------------------------------ 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 65d5fbb25c89357a83bc940bc9b060f46d7bd93a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 65d5fbb25c89357a83bc940bc9b060f46d7bd93a Commit message: "drop EOL 4.1 appliance builds and jobs" > git rev-list --no-walk 65d5fbb25c89357a83bc940bc9b060f46d7bd93a # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins6991449812731049270.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 1443, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-qemu-ev-testing-el7/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 3

[JIRA] (OVIRT-2056) All CQ failing due to ovirt-4.1 centos being EOL
by Dafna Ron (oVirt JIRA) 25 May '18

25 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2056?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2056: ---------------------------------- builds are running again for both master and 4.2 I re-added changes from projects that do not run often > All CQ failing due to ovirt-4.1 centos being EOL > ------------------------------------------------ > > Key: OVIRT-2056 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2056 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > 21:50:07 [upgrade-from-release-suit] raise e > 21:50:07 [upgrade-from-release-suit] yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from centos-ovirt-4.1-el7: [Errno 256] No more mirrors to try. > 21:50:07 [upgrade-from-release-suit] http://mirror.centos.org/centos/7.4.1708/virt/x86_64/ovirt-4.1/repodata/rep…: [Errno 14] HTTP Error 404 - Not Found > 21:50:07 [upgrade-from-release-suit] > 21:50:07 [upgrade-from-release-suit] * Running reposync: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] # Syncing remote repos locally (this might take some time): ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] @ Create prefix internal repo: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] Error occured, aborting -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 224 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

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.2/… Build Number: 224 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #224 [Sandro Bonazzola] repos: adding cockpit-machines-ovirt [Eyal Edri] drop ngn 4.1 jobs since oVirt 4.1 is EOL [Eyal Edri] drop EOL 4.1 appliance builds and jobs ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt CI] standard-enqueue - Build #13754 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13754/ Build Name: #13754 Build Description: Gerrit: 91619 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91619 - title: build: ovirt-engine-3.6.13.5 - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 1

[CQ]: 91561, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 25 May '18

25 May '18

Change 91561,1 (ovirt-engine-metrics) 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/91561/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7772/

1 0

[JIRA] (OVIRT-2057) fix plain.resources HTTPS vhost
by Evgheni Dereveanchin (oVirt JIRA) 25 May '18

25 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2057?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2057: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > fix plain.resources HTTPS vhost > ------------------------------- > > Key: OVIRT-2057 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2057 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Currently https://plain.resources.ovirt.org looks the same as https://resources.ovirt.org - this should be fixed and can be done by adding the servername parameter as currently the vhost name is used which does not match the FQDN so SNI never uses it: > <VirtualHost *:443> > ServerName plain.resources.ovirt.org-ssl -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2057) fix plain.resources HTTPS vhost
by Evgheni Dereveanchin (oVirt JIRA) 25 May '18

25 May '18

Evgheni Dereveanchin created OVIRT-2057: ------------------------------------------- Summary: fix plain.resources HTTPS vhost Key: OVIRT-2057 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2057 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Currently https://plain.resources.ovirt.org looks the same as https://resources.ovirt.org - this should be fixed and can be done by adding the servername parameter as currently the vhost name is used which does not match the FQDN so SNI never uses it: <VirtualHost *:443> ServerName plain.resources.ovirt.org-ssl -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2056) All CQ failing due to ovirt-4.1 centos being EOL
by Dafna Ron (oVirt JIRA) 25 May '18

25 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2056?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2056: ---------------------------------- 4.1 needs to be 7.4 for the upgrade so we couldn't change it to 7.5 image. I spoke to Barak and he suggested I look for other centos repos which we can use. I found: http://vault.centos.org/ I replaced both virt and gluster repos. https://gerrit.ovirt.org/#/c/91628/ > All CQ failing due to ovirt-4.1 centos being EOL > ------------------------------------------------ > > Key: OVIRT-2056 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2056 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > 21:50:07 [upgrade-from-release-suit] raise e > 21:50:07 [upgrade-from-release-suit] yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from centos-ovirt-4.1-el7: [Errno 256] No more mirrors to try. > 21:50:07 [upgrade-from-release-suit] http://mirror.centos.org/centos/7.4.1708/virt/x86_64/ovirt-4.1/repodata/rep…: [Errno 14] HTTP Error 404 - Not Found > 21:50:07 [upgrade-from-release-suit] > 21:50:07 [upgrade-from-release-suit] * Running reposync: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] # Syncing remote repos locally (this might take some time): ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] @ Create prefix internal repo: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] Error occured, aborting -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[oVirt CI] standard-enqueue - Build #13748 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13748/ Build Name: #13748 Build Description: Gerrit: 91626 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91626 - title: engine: try to find CPU with \",+spec-ctrl\" if \"-IBRS\" is not found - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Tomas Jelinek <tjelinek(a)redhat.com>

1 2

[CQ]: 91611, 1 (ovirt-host) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '18

25 May '18

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

1 0

[oVirt CI] standard-enqueue - Build #13745 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13745/ Build Name: #13745 Build Description: Gerrit: 91622 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91622 - title: engine: try to find CPU with \",+spec-ctrl\" if \"-IBRS\" is not found - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Michal Skrivanek <michal.skrivanek(a)redhat.com>

1 0

[JIRA] (OVIRT-2056) All CQ failing due to ovirt-4.1 centos being EOL
by Dafna Ron (oVirt JIRA) 25 May '18

25 May '18

Dafna Ron created OVIRT-2056: -------------------------------- Summary: All CQ failing due to ovirt-4.1 centos being EOL Key: OVIRT-2056 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2056 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra 21:50:07 [upgrade-from-release-suit] raise e 21:50:07 [upgrade-from-release-suit] yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from centos-ovirt-4.1-el7: [Errno 256] No more mirrors to try. 21:50:07 [upgrade-from-release-suit] http://mirror.centos.org/centos/7.4.1708/virt/x86_64/ovirt-4.1/repodata/rep…: [Errno 14] HTTP Error 404 - Not Found 21:50:07 [upgrade-from-release-suit] 21:50:07 [upgrade-from-release-suit] * Running reposync: ERROR (in 0:00:01) 21:50:07 [upgrade-from-release-suit] # Syncing remote repos locally (this might take some time): ERROR (in 0:00:01) 21:50:07 [upgrade-from-release-suit] @ Create prefix internal repo: ERROR (in 0:00:01) 21:50:07 [upgrade-from-release-suit] Error occured, aborting -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91489,2 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 25 May '18

25 May '18

Change 91489,2 (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/91489/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2018/

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 49 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build Number: 49 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #49 [Emil Natan] Add Emil's email alias to whitelist [Martin Perina] wildfly: wildfly-overlay: Add FC28 builds [Martin Perina] engine-extensions: Add FC28 builds [Barak Korren] Don't run check-patch-s390x.sh on merge [Evgheni Dereveanchin] Verify Jenkins user settings from global_setup [Yuval Turgeman] Revert "Test building with ansible25" ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 91524,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 25 May '18

25 May '18

Change 91524,2 (ovirt-provider-ovn) 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/91524/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2016/

1 0

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

25 May '18

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

1 0

[CQ]: 91524,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 25 May '18

25 May '18

Change 91524,2 (ovirt-provider-ovn) 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/91524/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2014/

1 0

CVE-2018-3639 - Important - oVirt - Speculative Store Bypass
by Sandro Bonazzola 25 May '18

25 May '18

As you may have already heard, an industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions. This issue is well described by CVE-2018-3639 announce available at https://access.redhat.com/security/cve/cve-2018-3639. oVirt team has released right now an update of ovirt-engine to version 4.2.3.7 which add support for SSBD CPUs in order to mitigate the security issue. If you are running oVirt on Red Hat Enterprise Linux, please apply updates described in https://access.redhat.com/security/cve/cve-2018-3639. If you are running oVirt on CentOS Linux please apply updated described by: CESA-2018:1629 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html> CESA-2018:1632 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022840.html> CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022839.html> CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022838.html> An update for qemu-kvm-ev has been also tagged for release and announced with CESA-2018:1655 Important: qemu-kvm-ev security update <https://lists.centos.org/pipermail/centos-virt/2018-May/005804.html> but due to some issues in CentOS release process for Virt SIG content, it is not yet available on mirrors. We are working with CentOS community to get the packages signed and published as soon as possible. In the meanwhile you can still get the update package by enabling the test repository https://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ on your systems or manually installing the package from the repository. If you're running oVirt on a different Linux distribution, please check with your vendor for available updates. Please note that to fully mitigate this vulnerability, system administrators must apply both hardware “microcode” updates and software patches that enable new functionality. At this time, microprocessor microcode will be delivered by the individual manufacturers. The oVirt team recommends end users and systems administrator to apply any available updates as soon as practical. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 1

[CQ]: 91331, 1 (ovirt-host) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '18

25 May '18

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

1 0

[CQ]: 90951, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '18

25 May '18

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

1 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 284 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 May '18

25 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x8… Build Number: 284 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #284 [Sandro Bonazzola] kickstart: drop upstream cockpit copr repo ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Barak Korren (oVirt JIRA) 25 May '18

25 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2054: ------------------------------------- {quote} Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? {quote} If its being used you will see in installed in the 'deploy' phase, or by engins-setup or during AddHost. The interesting thing here is why did the CQ test fail if the patch is not being actually tested. > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91042, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 May '18

25 May '18

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

1 0