[JENKINS] Failed to setup proejct
kubevirt_ovs-cni_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#173 ovs-cni [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-ld8t4.
5 years, 11 months
Build failed in Jenkins:
system-sync_mirrors-centos-kvm-common-el7-x86_64 #1980
by jenkins@jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x8...>
------------------------------------------
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-kvm-common-el7-x8...>
> 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/changes/59/95959/1:test --prune
> git rev-parse origin/test^{commit} # timeout=10
> git rev-parse test^{commit} # timeout=10
Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test)
> git config core.sparsecheckout # timeout=10
> git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1
Commit message: "mirror-reposync: remove gluster-3.10 mirror"
> git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10
[system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1507560353657937336.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-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-kvm-common-el7/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7/packages'
Build step 'Execute shell' marked build as failure
5 years, 11 months
[JIRA] (OVIRT-2616) Rawhide build failed, not logs available
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2616?page=com.atlassian.jir... ]
Daniel Belenky commented on OVIRT-2616:
---------------------------------------
The build summary doesn't point to a log because it doesn't exist yet.
That's why see "Testing system error" message on that substage.
You can have a look in Blue Ocean and see the logs from the CI system
itself here
<https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-imageio_standa...>
.
On Thu, Dec 6, 2018 at 12:05 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
> On Thu, Dec 6, 2018, 11:16 Daniel Belenky <dbelenky(a)redhat.com wrote:
>
>> Hi Nir,
>>
>> The rawhide substage failed to install `python2-docker`.
>>
>
> Can you point me to the log with this error?
>
> Why the build log was missing?
>
> Maybe the build sammary html should point to a differrent log for such
> failures?
>
> I think it was a temporary issue with the rawhide repo. We don't mirror it.
>>
>> On Wed, Dec 5, 2018 at 11:21 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/arti...
>>>
>>>
>>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//art...
>>> returns 404
>>>
>>> The next builds on this topic succeeded, so it probably was a temporary
>>> error. Do we have any other
>>> log that can explain what happened on the slave running the rawhide
>>> build?
>>>
>>>
>>> Nir
>>> _______________________________________________
>>> Infra mailing list -- infra(a)ovirt.org
>>> To unsubscribe send an email to infra-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/infra@ovirt.org/message/FFF7KZJ4BSZ...
>>>
>>
>>
>> --
>>
>> DANIEL BELENKY
>>
>
--
DANIEL BELENKY
> Rawhide build failed, not logs available
> ----------------------------------------
>
> Key: OVIRT-2616
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2616
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/arti...
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//art...
> returns 404
> The next builds on this topic succeeded, so it probably was a temporary
> error. Do we have any other
> log that can explain what happened on the slave running the rawhide build?
> Nir
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
5 years, 11 months
[JIRA] (OVIRT-2616) Rawhide build failed, not logs available
by Nir Soffer (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2616?page=com.atlassian.jir... ]
Nir Soffer commented on OVIRT-2616:
-----------------------------------
On Thu, Dec 6, 2018, 11:16 Daniel Belenky <dbelenky(a)redhat.com wrote:
> Hi Nir,
>
> The rawhide substage failed to install `python2-docker`.
>
Can you point me to the log with this error?
Why the build log was missing?
Maybe the build sammary html should point to a differrent log for such
failures?
I think it was a temporary issue with the rawhide repo. We don't mirror it.
>
> On Wed, Dec 5, 2018 at 11:21 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
>
>>
>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/arti...
>>
>>
>> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//art...
>> returns 404
>>
>> The next builds on this topic succeeded, so it probably was a temporary
>> error. Do we have any other
>> log that can explain what happened on the slave running the rawhide build?
>>
>>
>> Nir
>> _______________________________________________
>> Infra mailing list -- infra(a)ovirt.org
>> To unsubscribe send an email to infra-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/infra@ovirt.org/message/FFF7KZJ4BSZ...
>>
>
>
> --
>
> DANIEL BELENKY
>
> Rawhide build failed, not logs available
> ----------------------------------------
>
> Key: OVIRT-2616
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2616
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723/arti...
> https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/723//art...
> returns 404
> The next builds on this topic succeeded, so it probably was a temporary
> error. Do we have any other
> log that can explain what happened on the slave running the rawhide build?
> Nir
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100095)
5 years, 11 months