May 2018 - Infra - oVirt List Archives

Updated docs on oVirt site and Mail service
by Eyal Edri 23 May '18

23 May '18

Hi, I was wondering if we have an official place where we keep docs on how we manage the oVirt web site and mail server, in case we'll need to update or debug an issue in any of the services. Ideally, we should have something under [1], can we add relevant links and info there? [1] http://ovirt-infra-docs.readthedocs.io/en/latest/ -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 1

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

23 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13642/ Build Name: #13642 Build Description: Gerrit: 91512 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91512 - title: build: ovirt-engine-4.2.3.7 - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 1

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

23 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13640/ Build Name: #13640 Build Description: Gerrit: 91509 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91509 - title: core: add SSBD CPUs - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Michal Skrivanek <michal.skrivanek(a)redhat.com>

1 0

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

23 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 73fa7d65045d749c46c791a74416adbba62fe887 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 73fa7d65045d749c46c791a74416adbba62fe887 Commit message: "Drop mock_runner support for FC25 and FC24" > git rev-list --no-walk 73fa7d65045d749c46c791a74416adbba62fe887 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins984243758019156706.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 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 906, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 23 May '18

23 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/155 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I245e8658317dc9ac36fb0e9607c5386255bae8f4 Gerrit-Change-Number: 155 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 23 May 2018 08:36:07 +0000 Gerrit-HasComments: No

1 0

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

23 May '18

A system test invoked by the "ovirt-master" change queue including change 91427,6 (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/91427/6 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/7687/

1 0

Change in ds-jenkins-stg[master]: Updated US source to: 28865d2 testing asdf
by review＠gerrit-staging.phx.ovirt.org 23 May '18

23 May '18

From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/155 ) Change subject: Updated US source to: 28865d2 testing asdf ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/155 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: ds-jenkins-stg Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I245e8658317dc9ac36fb0e9607c5386255bae8f4 Gerrit-Change-Number: 155 Gerrit-PatchSet: 1 Gerrit-Owner: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Wed, 23 May 2018 08:20:31 +0000 Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-2050) Make a landing page for STDCI builds
by Daniel Belenky (oVirt JIRA) 23 May '18

23 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2050?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2050: ---------------------------------- Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do) > Make a landing page for STDCI builds > ------------------------------------ > > Key: OVIRT-2050 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2050 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Since STDCI V2 executes the major build steps (running user script) on different nodes, it's hard to understand > the status/what failed from console output. The alternative is to use Blue Ocean view but it takes ~40 seconds to > load in some cases. > The first phase is to build a status report at the end of every STDCI build with quick access to relevant links such as logs, artifacts, test results and etc. > In the long term, the plan is to integrate "real time" updates such as console output updates per thread and etc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2050) Make a landing page for STDCI builds
by Daniel Belenky (oVirt JIRA) 23 May '18

23 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2050?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2050: ---------------------------------- Epic Link: OVIRT-400 > Make a landing page for STDCI builds > ------------------------------------ > > Key: OVIRT-2050 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2050 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > Since STDCI V2 executes the major build steps (running user script) on different nodes, it's hard to understand > the status/what failed from console output. The alternative is to use Blue Ocean view but it takes ~40 seconds to > load in some cases. > The first phase is to build a status report at the end of every STDCI build with quick access to relevant links such as logs, artifacts, test results and etc. > In the long term, the plan is to integrate "real time" updates such as console output updates per thread and etc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2050) Make a landing page for STDCI builds
by Daniel Belenky (oVirt JIRA) 23 May '18

23 May '18

Daniel Belenky created OVIRT-2050: ------------------------------------- Summary: Make a landing page for STDCI builds Key: OVIRT-2050 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2050 Project: oVirt - virtualization made easy Issue Type: Bug Components: Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra Since STDCI V2 executes the major build steps (running user script) on different nodes, it's hard to understand the status/what failed from console output. The alternative is to use Blue Ocean view but it takes ~40 seconds to load in some cases. The first phase is to build a status report at the end of every STDCI build with quick access to relevant links such as logs, artifacts, test results and etc. In the long term, the plan is to integrate "real time" updates such as console output updates per thread and etc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0