- Infra - oVirt List Archives

[CQ]: 103556, 4 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 29 Oct '19

29 Oct '19

Change 103556,4 (ovirt-system-tests) 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/103556/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16682/

1 0

[JIRA] (OVIRT-2814) reposync fails syncing repos on completely unrelated paths (concurrency issue?)
by Anton Marchukov (oVirt JIRA) 29 Oct '19

29 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2814?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2814: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > reposync fails syncing repos on completely unrelated paths (concurrency issue?) > ------------------------------------------------------------------------------- > > Key: OVIRT-2814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI Mirrors > Reporter: Sandro Bonazzola > Assignee: Evgheni Dereveanchin > > About job > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > As you can see below > 05:35:07 ++ reposync --config=jenkins/data/mirrors-reposync.conf > --repoid=centos-kvm-common-el7 --arch=x86_64 > --cachedir=/home/jenkins/mirrors_cache > --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base > --norepopath --newest-only --urls --quiet > the sync is related to "/var/www/html/repos/yum/centos-kvm-common-el7/base" > using as cache directory "/home/jenkins/mirrors_cache" > but in "/home/jenkins/mirrors_cache" there's > "/home/jenkins/mirrors_cache/fedora-base-fc29": > 05:35:16 Traceback (most recent call last): > 05:35:16 File "/usr/bin/reposync", line 373, in <module> > 05:35:16 main() > 05:35:16 File "/usr/bin/reposync", line 185, in main > 05:35:16 my.doRepoSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 681, in doRepoSetup > 05:35:16 return self._getRepos(thisrepo, True) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 721, in _getRepos > 05:35:16 self._repos.doSetup(thisrepo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, > in doSetup > 05:35:16 self.retrieveAllMD() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, > in retrieveAllMD > 05:35:16 dl = repo._async and repo._commonLoadRepoXML(repo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 1468, in _commonLoadRepoXML > 05:35:16 local = self.cachedir + '/repomd.xml' > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 777, in <lambda> > 05:35:16 cachedir = property(lambda self: self._dirGetAttr('cachedir')) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 760, in _dirGetAttr > 05:35:16 self.dirSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 738, in dirSetup > 05:35:16 self._dirSetupMkdir_p(dir) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 715, in _dirSetupMkdir_p > 05:35:16 raise Errors.RepoError, msg > 05:35:16 yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File > exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' > this looks like a concurrency issue, a lock should be used in order to > prevent two instances to use the same cache directory at the same time or > use separate cache directories for different repos. > -- > Sandro Bonazzola -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2814) reposync fails syncing repos on completely unrelated paths (concurrency issue?)
by Anton Marchukov (oVirt JIRA) 29 Oct '19

29 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2814?page=com.atlassian.jira.… ] Anton Marchukov reopened OVIRT-2814: ------------------------------------ > reposync fails syncing repos on completely unrelated paths (concurrency issue?) > ------------------------------------------------------------------------------- > > Key: OVIRT-2814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI Mirrors > Reporter: Sandro Bonazzola > Assignee: infra > > About job > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > As you can see below > 05:35:07 ++ reposync --config=jenkins/data/mirrors-reposync.conf > --repoid=centos-kvm-common-el7 --arch=x86_64 > --cachedir=/home/jenkins/mirrors_cache > --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base > --norepopath --newest-only --urls --quiet > the sync is related to "/var/www/html/repos/yum/centos-kvm-common-el7/base" > using as cache directory "/home/jenkins/mirrors_cache" > but in "/home/jenkins/mirrors_cache" there's > "/home/jenkins/mirrors_cache/fedora-base-fc29": > 05:35:16 Traceback (most recent call last): > 05:35:16 File "/usr/bin/reposync", line 373, in <module> > 05:35:16 main() > 05:35:16 File "/usr/bin/reposync", line 185, in main > 05:35:16 my.doRepoSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 681, in doRepoSetup > 05:35:16 return self._getRepos(thisrepo, True) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 721, in _getRepos > 05:35:16 self._repos.doSetup(thisrepo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, > in doSetup > 05:35:16 self.retrieveAllMD() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, > in retrieveAllMD > 05:35:16 dl = repo._async and repo._commonLoadRepoXML(repo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 1468, in _commonLoadRepoXML > 05:35:16 local = self.cachedir + '/repomd.xml' > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 777, in <lambda> > 05:35:16 cachedir = property(lambda self: self._dirGetAttr('cachedir')) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 760, in _dirGetAttr > 05:35:16 self.dirSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 738, in dirSetup > 05:35:16 self._dirSetupMkdir_p(dir) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 715, in _dirSetupMkdir_p > 05:35:16 raise Errors.RepoError, msg > 05:35:16 yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File > exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' > this looks like a concurrency issue, a lock should be used in order to > prevent two instances to use the same cache directory at the same time or > use separate cache directories for different repos. > -- > Sandro Bonazzola -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2814) reposync fails syncing repos on completely unrelated paths (concurrency issue?)
by Anton Marchukov (oVirt JIRA) 29 Oct '19

29 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2814?page=com.atlassian.jira.… ] Anton Marchukov closed OVIRT-2814. ---------------------------------- > reposync fails syncing repos on completely unrelated paths (concurrency issue?) > ------------------------------------------------------------------------------- > > Key: OVIRT-2814 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2814 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI Mirrors > Reporter: Sandro Bonazzola > Assignee: infra > > About job > https://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86… > As you can see below > 05:35:07 ++ reposync --config=jenkins/data/mirrors-reposync.conf > --repoid=centos-kvm-common-el7 --arch=x86_64 > --cachedir=/home/jenkins/mirrors_cache > --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base > --norepopath --newest-only --urls --quiet > the sync is related to "/var/www/html/repos/yum/centos-kvm-common-el7/base" > using as cache directory "/home/jenkins/mirrors_cache" > but in "/home/jenkins/mirrors_cache" there's > "/home/jenkins/mirrors_cache/fedora-base-fc29": > 05:35:16 Traceback (most recent call last): > 05:35:16 File "/usr/bin/reposync", line 373, in <module> > 05:35:16 main() > 05:35:16 File "/usr/bin/reposync", line 185, in main > 05:35:16 my.doRepoSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 681, in doRepoSetup > 05:35:16 return self._getRepos(thisrepo, True) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/__init__.py", line > 721, in _getRepos > 05:35:16 self._repos.doSetup(thisrepo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, > in doSetup > 05:35:16 self.retrieveAllMD() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, > in retrieveAllMD > 05:35:16 dl = repo._async and repo._commonLoadRepoXML(repo) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 1468, in _commonLoadRepoXML > 05:35:16 local = self.cachedir + '/repomd.xml' > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 777, in <lambda> > 05:35:16 cachedir = property(lambda self: self._dirGetAttr('cachedir')) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 760, in _dirGetAttr > 05:35:16 self.dirSetup() > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 738, in dirSetup > 05:35:16 self._dirSetupMkdir_p(dir) > 05:35:16 File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line > 715, in _dirSetupMkdir_p > 05:35:16 raise Errors.RepoError, msg > 05:35:16 yum.Errors.RepoError: Error making cache directory: > /home/jenkins/mirrors_cache/fedora-base-fc29 error was: [Errno 17] File > exists: '/home/jenkins/mirrors_cache/fedora-base-fc29' > this looks like a concurrency issue, a lock should be used in order to > prevent two instances to use the same cache directory at the same time or > use separate cache directories for different repos. > -- > Sandro Bonazzola -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

Fwd: IMPORTANT: OST is now gated.
by Ehud Yonasi 29 Oct '19

29 Oct '19

We are going to merge the patch to enable the gating today [1]. Please watch carefully for OST patches if they don't pass the gate and find out why. [1]: https://gerrit.ovirt.org/#/c/103556/ ---------- Forwarded message --------- From: Milan Zamazal <mzamazal(a)redhat.com> Date: Wed, Sep 25, 2019 at 4:48 PM Subject: Re: IMPORTANT: OST is now gated. To: Ehud Yonasi <eyonasi(a)redhat.com> Cc: devel <devel(a)ovirt.org> Ehud Yonasi <eyonasi(a)redhat.com> writes: > Hey everyone, > OST project is now enabled for patch gating. Hi, it's cool, but before enabling it for other projects, please make sure pending OST problems are fixed. AFAIK the random failures related to add_master_storage_domain in basic-suite-master and discussed here recently haven't been fixed yet (and I think this was the random failure I observed when running OST on my computer yesterday). While random failures may not look that urgent as regular failures, they are still incompatible with patch gating and will cause trouble in projects with more frequent merges and/or longer patch series. Thanks, Milan > What is the meaning of this? > > 1. The gating process will start when Code-Review +2, CI +1 and > Verified +1 labels are turned on. > 2. Every patch before merging will have to pass the following suites: > - > > *oVirt-master* > > *oVirt-4.3* > > basic_suite > > basic_suite > > upgrade-from-release > > upgrade-from-release > > > upgrade-from-prevrelease > 3. Patches should no longer be manually merged in OST, they will be > merged automatically when passing the gate. > > *NOTE: *Maintainers are still able to merge manually, but it is not > recommended if the gate is not passing. > > *NOTE:* For additional information regarding the gating I've sent FAQ mail > - 'Patch Gating summary + FAQ' > > Regards, > Ehud. > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZES5BD3FXCKHD…

1 0

[CQ]: 4d9fdcd (ovirt-engine-sdk-go) failed "ovirt-4.3" system tests
by oVirt Jenkins 29 Oct '19

29 Oct '19

Change 4d9fdcd (ovirt-engine-sdk-go) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-engine-sdk-go/commit/4d9fdcd42d8317a66234fe2… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2349/

1 0

[CQ]: 3e18995 (ovirt-engine-sdk-go) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Oct '19

29 Oct '19

A system test invoked by the "ovirt-master" change queue including change 3e18995 (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) 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://github.com/oVirt/ovirt-engine-sdk-go/commit/3e189957a5bd4eeb9c6a3c6… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16674/

1 0

[CQ]: 9725eea (ovirt-engine-sdk-go) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Oct '19

29 Oct '19

A system test invoked by the "ovirt-master" change queue including change 9725eea (ovirt-engine-sdk-go) failed. However, this change seems not to be the root cause for this failure. Change fbbe965 (ovirt-engine-sdk-go) 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 fbbe965 (ovirt-engine-sdk-go) 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://github.com/oVirt/ovirt-engine-sdk-go/commit/9725eea12cfc6fac2405db3… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-engine-sdk-go/commit/fbbe96561752bb82969ddd6… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16672/

1 0

oVirt infra daily report - unstable production jobs - 992
by jenkins＠jenkins.phx.ovirt.org 29 Oct '19

29 Oct '19

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/992//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 104263, 2 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Oct '19

28 Oct '19

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

1 0