September 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results

by Emil Natan (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jir... ] Emil Natan updated OVIRT-2501: ------------------------------ Resolution: Duplicate Status: Done (was: To Do) duplicates - OVIRT-1447 > Add gerrit comment about actual CQ results > ------------------------------------------ > > Key: OVIRT-2501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I do not know how the CQ works, or even the terminology. Sorry. > When a patch is merged in gerrit, some time later a job is triggered > that adds it to the CQ. This job adds a link like [1]. > Later, the CQ tests the batch of changes, and either approves them or > bisects them to try to find the bad one. I can't see in the gerrit > page, e.g. [2], any comment from this part. Please make the relevant > jobs add suitable comments to relevant gerrit changes. E.g. "This > change passed the CQ <link>", or failed, or some other suspect change > failed and therefore this one isn't published either, or whatever. > [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ > [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

5 years, 9 months

1
0
0 / 0

[CQ Failure Report] [oVirt Master - ovirt-engine] [16/9/18] [basic-suite.el7.x86_64]

by Ehud Yonasi

Hey everyone, We have a failure in CQ on the test of verify_add_hosts. Link to error: https://pastebin.com/Bwqn19Pn Link to the CQ job: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...

5 years, 9 months

2
1
0 / 0

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results

by Emil Natan (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jir... ] Emil Natan commented on OVIRT-2501: ----------------------------------- duplicates OVIRT-1447 > Add gerrit comment about actual CQ results > ------------------------------------------ > > Key: OVIRT-2501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I do not know how the CQ works, or even the terminology. Sorry. > When a patch is merged in gerrit, some time later a job is triggered > that adds it to the CQ. This job adds a link like [1]. > Later, the CQ tests the batch of changes, and either approves them or > bisects them to try to find the bad one. I can't see in the gerrit > page, e.g. [2], any comment from this part. Please make the relevant > jobs add suitable comments to relevant gerrit changes. E.g. "This > change passed the CQ <link>", or failed, or some other suspect change > failed and therefore this one isn't published either, or whatever. > [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ > [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

5 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2501?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2501: ---------------------------------- CQ is not completely automated and what I mean by that is that we (i.e me/infra owners) need to look at the failures and determine if the cause of failure/root cause of failure or some other patch is responsible. Having said that, we want, in future, to involve the developers automatically at an earlier stage then this one but we are still considering several solutions for this. > Add gerrit comment about actual CQ results > ------------------------------------------ > > Key: OVIRT-2501 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I do not know how the CQ works, or even the terminology. Sorry. > When a patch is merged in gerrit, some time later a job is triggered > that adds it to the CQ. This job adds a link like [1]. > Later, the CQ tests the batch of changes, and either approves them or > bisects them to try to find the bad one. I can't see in the gerrit > page, e.g. [2], any comment from this part. Please make the relevant > jobs add suitable comments to relevant gerrit changes. E.g. "This > change passed the CQ <link>", or failed, or some other suspect change > failed and therefore this one isn't published either, or whatever. > [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ > [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

5 years, 9 months

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 197 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64... Build Number: 197 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #197 [Gal Ben Haim] Add jobs for ovs-cni [Ryan Barry] kickstart: let VDSM reconfigure itself ----------------- Failed Tests: ----------------- No tests ran.

5 years, 9 months

1
4
0 / 0

[JIRA] (OVIRT-2463) http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

by Yedidyah Bar David (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2463?page=com.atlassian.jir... ] Yedidyah Bar David commented on OVIRT-2463: ------------------------------------------- Any update? https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... 06:03:03 + yum install --nogpgcheck --downloaddir=/dev/shm -y ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' otopi-debug-plugins cronie 06:03:03 http://192.168.200.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found 06:03:03 Error: Package: ovirt-engine-4.3.0-0.0.master.20180916101831.gitd855858.el7.noarch (alocalsync) 06:03:03 Requires: nimbus-jose-jwt >= 5.12 > http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2463 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2463 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue > Reporter: Anton Marchukov > Assignee: infra > Labels: ost_failures > > Project name: > ovirt-ansible-engine-setup > Branch: > master > Failed Suite: > upgrade-from-release-suite.el7.x86_64 > Failed test/failed phase: > 001_upgrade_engine.test_initialize_engine > Link to first reported failed build: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/9255/ > Link to first reported failed patch: > ??? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

5 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-2501) Add gerrit comment about actual CQ results

by Yedidyah Bar David (oVirt JIRA)

Yedidyah Bar David created OVIRT-2501: ----------------------------------------- Summary: Add gerrit comment about actual CQ results Key: OVIRT-2501 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2501 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Yedidyah Bar David Assignee: infra Hi all, I do not know how the CQ works, or even the terminology. Sorry. When a patch is merged in gerrit, some time later a job is triggered that adds it to the CQ. This job adds a link like [1]. Later, the CQ tests the batch of changes, and either approves them or bisects them to try to find the bad one. I can't see in the gerrit page, e.g. [2], any comment from this part. Please make the relevant jobs add suitable comments to relevant gerrit changes. E.g. "This change passed the CQ <link>", or failed, or some other suspect change failed and therefore this one isn't published either, or whatever. [1] https://jenkins.ovirt.org/job/standard-enqueue/16271/ [2] https://gerrit.ovirt.org/#/c/94106/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100092)

5 years, 9 months

1
0
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1869/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 f9508e32027645ea57bcfec09dafe628fbb06677 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f9508e32027645ea57bcfec09dafe628fbb06677 Commit message: "standard_pipelines: add nmstate project" > git rev-list --no-walk f9508e32027645ea57bcfec09dafe628fbb06677 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins2411326242761979621.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/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/packages' Build step 'Execute shell' marked build as failure

5 years, 9 months

1
1
0 / 0

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #343

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/343/display/r...>

5 years, 9 months

1
3
0 / 0

oVirt infra daily report - unstable production jobs - 585

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/585//artifact/exported... Cheers, Jenkins

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2018