May 2018 - Infra - Ovirt List Archives

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

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/13584/ Build Name: #13584 Build Description: Gerrit: 91453 - ovirt-engine (3.6) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91453 - title: core: Fill jackson deserialization whitelist - project: ovirt-engine - branch: ovirt-engine-3.6 - author: Martin Peřina <mperina(a)redhat.com>

6 years, 7 months

1
1
0 / 0

[JIRA] (OVIRT-2038) oVirt dashboard is not being updated

by Marc Dequènes (Duck) (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2038?page=com.atlassian.jir... ] Marc Dequènes (Duck) reassigned OVIRT-2038: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > oVirt dashboard is not being updated > ------------------------------------ > > Key: OVIRT-2038 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2038 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Marc Dequènes (Duck) > Attachments: signature.asc, signature.asc, signature.asc > > > Hi, > looking at https://ovirt.org/dashboard/ I see that latest data are from > March while http://ovirt.biterg.io/ is updated to today. > Can you please check what's got broken in data retrieval from bitergia? > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/13577/ Build Name: #13577 Build Description: Gerrit: 91369 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91369 - title: engine: added support for sending vm cpu flags according to cluster - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Tomas Jelinek <tjelinek(a)redhat.com>

6 years, 7 months

1
2
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/standard-enqueue/13573/ Build Name: #13573 Build Description: Gerrit: 91368 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91368 - title: engine: added support for sending vm cpu flags according to cluster - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Tomas Jelinek <tjelinek(a)redhat.com>

6 years, 7 months

1
2
0 / 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order

by Piotr Kliczewski (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jir... ] Piotr Kliczewski commented on OVIRT-1759: ----------------------------------------- Yes, I am guilty of this one. I often do that and as far as I know other people are doing it. If that is the issue I can trigger merges one by one but we would have usablility issue :|. > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1759: ------------------------------------- {quote} I think 1 hour should suffice, but it depends on how loaded the CQ is, Barak Korren any thoughts? {quote} There is no need to wait one hour and this has nothing to do with the delay between merging 'vdsm-jsonrpc-java' and 'ovirt-engine'. The issue discussed in this ticket is triggered when reviewing a series of patches and merging all of then together by clicking the "submit with parents" button on a child patch in Gerrit. As long as patches are merged individually by clicking on the "merge" button for each one the issue shouldn't arise. This issue should not be confused with the need to do dependency handling so that equivalent versions of engine and 'vdsm-jsonrpc-java' are tested together. That is tracked in OVIRT-1662. > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1506/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 43cf7bc564f91ced28faf91e1ef6b59ac5e038b7 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 43cf7bc564f91ced28faf91e1ef6b59ac5e038b7 Commit message: "Verify Jenkins user settings from global_setup" > git rev-list --no-walk 43cf7bc564f91ced28faf91e1ef6b59ac5e038b7 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins7569116168862018092.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

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 229 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/229/ Build Number: 229 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #229 [Sandro Bonazzola] repos: adding cockpit-machines-ovirt [Evgheni Dereveanchin] Verify Jenkins user settings from global_setup ----------------- Failed Tests: ----------------- No tests ran.

6 years, 7 months

1
1
0 / 0

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 329 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/... Build Number: 329 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #329 [Sandro Bonazzola] repos: adding cockpit-machines-ovirt [Evgheni Dereveanchin] Verify Jenkins user settings from global_setup ----------------- Failed Tests: ----------------- No tests ran.

6 years, 7 months

1
1
0 / 0

[JIRA] (OVIRT-2038) oVirt dashboard is not being updated

by Marc Dequènes (Duck) (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2038?page=com.atlassian.jir... ] Marc Dequènes (Duck) commented on OVIRT-2038: --------------------------------------------- The redirection is done. The cleanup needs review here: https://github.com/oVirt/ovirt-site/pull/1624 > oVirt dashboard is not being updated > ------------------------------------ > > Key: OVIRT-2038 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2038 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > Attachments: signature.asc, signature.asc, signature.asc > > > Hi, > looking at https://ovirt.org/dashboard/ I see that latest data are from > March while http://ovirt.biterg.io/ is updated to today. > Can you please check what's got broken in data retrieval from bitergia? > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2018