[JIRA] (OVIRT-2054) false change reported since package is not
deployed on ost
by Dafna Ron (oVirt JIRA)
Dafna Ron created OVIRT-2054:
--------------------------------
Summary: false change reported since package is not deployed on ost
Key: OVIRT-2054
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Dafna Ron
Assignee: infra
Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/
The package is not deployed on OST so it could not have been the reason for failure.
+ I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report.
Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100086)
6 years, 6 months
oVirt Privacy policy change
by Sandro Bonazzola
*As part of an oVirt project review, we're publishing an updated privacy
policy.You should read the statement fully, but the key updates include:*
Clearer descriptions of how oVirt uses your personal data to provide
services;* Additional detail on how your personal data may be shared to
serve the public interest and that of the open source community; and* More
focus on how you can review, modify, and update your personal data.You can
find the new statement on the oVirt website at this location:
https://ovirt.org/site/privacy-policy/
<https://ovirt.org/site/privacy-policy/>oVirt website pages have been
updated to include links to the privacy policy. The new privacy statement
takes effect on Friday, May 25, 2018. *
--
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>
6 years, 6 months
Build failed in Jenkins:
system-sync_mirrors-fedora-updates-fc27-x86_64 #556
by jenkins@jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc27-x86_...>
Changes:
[Daniel Belenky] global_setup to ensure ownership of ~/.ssh
[Daniel Belenky] checkout_repo to tag every build
------------------------------------------
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-fedora-updates-fc27-x86_...>
> 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 9e5273d12dda68e1fc306be58c3a26e3e3d66e30 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 9e5273d12dda68e1fc306be58c3a26e3e3d66e30
Commit message: "checkout_repo to tag every build"
> git rev-list --no-walk 73fa7d65045d749c46c791a74416adbba62fe887 # timeout=10
[system-sync_mirrors-fedora-updates-fc27-x86_64] $ /bin/bash -xe /tmp/jenkins3939764987152376278.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc27 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Resyncing repo: fedora-updates-fc27
Syncing yum repo fedora-updates-fc27 for arch: x86_64
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-qemu-ev-release-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-qemu-ev-release-el7/gen'
Build step 'Execute shell' marked build as failure
6 years, 6 months