- Infra - oVirt List Archives

[CQ]: 84635,14 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 84635,14 (vdsm) 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/84635/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5613/

1 0

[JIRA] (OVIRT-1893) Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead
by eyal edri (oVirt JIRA) 12 Feb '18

12 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1893?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1893: ---------------------------------- The best way to solve it is to release a newer version than 1.1 with the fix, removing deployed versions from yum repos is not recommended and can cause issues to users/qe who is already using that repo. Also, master repo is pointing on nightly compose, not official release, you might want to use the 4.2 release rpm which includes only official releases ( and might also include the 0.1 version you're looking for ). [~sbonazzo@redhat.com][~bkorren@redhat.com] > Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead > ------------------------------------------------------------------------------------------ > > Key: OVIRT-1893 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1893 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Maor Lipchuk > Assignee: infra > > Hi all, > It seems that ovirt-ansible-disaster-recovery repo installed from upstream > [1] is installed with version 1.1 [2]: > ovirt-ansible-disaster-recovery-1.1 is broken, because of a bug which was > already fixed [3] in ovirt-ansible-disaster-recovery 0.1. > The thing is that the release which automatically installed is 1.1 although > the fix is available in ovirt-ansible-disaster-recovery 0.1. > Is there a way to do something about it, could we remove the 1.1 versions, > so 0.1 will be installed instead? > [1] http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2] > ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch > [3] https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4 > Regards, > Maor -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1268
by jenkins＠jenkins.phx.ovirt.org 12 Feb '18

12 Feb '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 5095e42a4078481a012b7133945333cfcb61af44 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 5095e42a4078481a012b7133945333cfcb61af44 Commit message: "ovirt-engine-metrics: re-align" > git rev-list 5095e42a4078481a012b7133945333cfcb61af44 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5318091456045681313.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/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/gen' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 87468, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87469, 1 (vdsm) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87467,1 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87459,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

Change 87459,1 (ovirt-engine) 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/87459/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/687/

1 0

[JIRA] (OVIRT-1893) Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead
by Maor Lipchuk (oVirt JIRA) 12 Feb '18

12 Feb '18

Maor Lipchuk created OVIRT-1893: ----------------------------------- Summary: Remove ovirt-ansible-disaster-recovery-1.1 upstream version to install version 0.1 instead Key: OVIRT-1893 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1893 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Maor Lipchuk Assignee: infra Hi all, It seems that ovirt-ansible-disaster-recovery repo installed from upstream [1] is installed with version 1.1 [2]: ovirt-ansible-disaster-recovery-1.1 is broken, because of a bug which was already fixed [3] in ovirt-ansible-disaster-recovery 0.1. The thing is that the release which automatically installed is 1.1 although the fix is available in ovirt-ansible-disaster-recovery 0.1. Is there a way to do something about it, could we remove the 1.1 versions, so 0.1 will be installed instead? [1] http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm [2] ovirt-ansible-disaster-recovery-1.1.0-0.1.master.20180104150940.el7.centos.noarch [3] https://github.com/oVirt/ovirt-ansible-disaster-recovery/pull/4 Regards, Maor -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[CQ]: 87477, 1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0

[CQ]: 87418,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 12 Feb '18

12 Feb '18

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

1 0