Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc24-x86_64 #147
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc24-x86_...>
------------------------------------------
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-fc24-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 bdca0b5702e3f2058805edcff168947ee95b1996 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f bdca0b5702e3f2058805edcff168947ee95b1996
> git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10
[system-sync_mirrors-fedora-updates-fc24-x86_64] $ /bin/bash -xe /tmp/hudson2711638654874449445.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc24 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Resyncing repo: fedora-updates-fc24
Syncing yum repo fedora-updates-fc24 for arch: x86_64
fedora-updates-fc24/presto 0% [ ] 0.0 B/s | 0 B --:-- ETA fedora-updates-fc24/presto 51% [======== ] 0.0 B/s | 834 kB --:-- ETA fedora-updates-fc24/prestodelta | 1.6 MB 00:00
(1/52): kernel-4.10.8-100.fc24.x86_64.rpm | 81 kB 00:00
(2/52): kernel-PAE-devel-4 1% [ ] 0.0 B/s | 3.0 MB --:-- ETA (2/52): kernel-PAE-devel-4.10.8-100.fc24.i686.rpm | 11 MB 00:00
(3/52): kernel-PAEdebug-de 9% [=- ] 9.9 MB/s | 19 MB 00:18 ETA (3/52): kernel-PAEdebug-devel-4.10.8-100.fc24.i686.rpm | 11 MB 00:00
(4/52): kernel-core-4.10.8 14% [== ] 11 MB/s | 29 MB 00:16 ETA (4/52): kernel-core-4.10.8 16% [==- ] 11 MB/s | 34 MB 00:15 ETA (4/52): kernel-core-4.10.8 18% [==- ] 11 MB/s | 37 MB 00:14 ETA (4/52): kernel-core-4.10.8 20% [=== ] 11 MB/s | 41 MB 00:14 ETA (4/52): kernel-core-4.10.8-100.fc24.x86_64.rpm | 20 MB 00:01
(5/52): kernel-cross-heade 23% [===- ] 11 MB/s | 47 MB 00:14 ETA (5/52): kernel-cross-headers-4.10.8-100.fc24.x86_64.rpm | 5.0 MB 00:00
(6/52): kernel-debug-4.10.8-100.fc24.x86_64.rpm | 81 kB 00:00
(7/52): kernel-debug-core- 25% [==== ] 11 MB/s | 53 MB 00:13 ETA (7/52): kernel-debug-core- 28% [==== ] 11 MB/s | 57 MB 00:13 ETA (7/52): kernel-debug-core- 29% [====- ] 11 MB/s | 61 MB 00:12 ETA (7/52): kernel-debug-core- 32% [===== ] 11 MB/s | 65 MB 00:12 ETA (7/52): kernel-debug-core-4.10.8-100.fc24.x86_64.rpm | 22 MB 00:01
(8/52): kernel-debug-devel 34% [===== ] 10 MB/s | 69 MB 00:13 ETA (8/52): kernel-debug-devel 35% [=====- ] 10 MB/s | 73 MB 00:12 ETA (8/52): kernel-debug-devel 37% [====== ] 10 MB/s | 77 MB 00:12 ETA (8/52): kernel-debug-devel-4.10.8-100.fc24.i686.rpm | 11 MB 00:01
(9/52): kernel-debug-devel 41% [======- ] 10 MB/s | 84 MB 00:11 ETA (9/52): kernel-debug-devel 42% [======- ] 10 MB/s | 87 MB 00:11 ETA (9/52): kernel-debug-devel 44% [======= ] 10 MB/s | 91 MB 00:11 ETA (9/52): kernel-debug-devel-4.10.8-100.fc24.x86_64.rpm | 11 MB 00:01
(10/52): kernel-debug-modu 46% [======= ] 9.3 MB/s | 94 MB 00:11 ETA (10/52): kernel-debug-modu 46% [======= ] 9.0 MB/s | 95 MB 00:12 ETA (10/52): kernel-debug-modu 47% [=======- ] 8.6 MB/s | 97 MB 00:12 ETA (10/52): kernel-debug-modu 48% [=======- ] 8.4 MB/s | 99 MB 00:12 ETA (10/52): kernel-debug-modu 49% [=======- ] 8.2 MB/s | 100 MB 00:12 ETA (10/52): kernel-debug-modu 50% [======== ] 8.0 MB/s | 102 MB 00:12 ETA (10/52): kernel-debug-modu 50% [======== ] 7.8 MB/s | 104 MB 00:12 ETA (10/52): kernel-debug-modu 51% [======== ] 7.6 MB/s | 106 MB 00:12 ETA (10/52): kernel-debug-modu 52% [======== ] 7.4 MB/s | 107 MB 00:13 ETA (10/52): kernel-debug-modu 53% [======== ] 7.1 MB/s | 108 MB 00:13 ETA (10/52): kernel-debug-modu 53% [========- ] 7.0 MB/s | 110 MB 00:13 ETA (10/52): kernel-debug-modu 54% [========- ] 6.8 MB/s | 111 MB 00:13 ETA (10/52): kernel-debug-modu 55% [========- ] 6.6 MB/s | 112 MB 00:13 ETA (10/52): kernel-debug-modu 55% [========- ] 6.4 MB/s | 114 MB 00:13 ETA (10/52): kernel-debug-modu 56% [========= ] 6.3 MB/s | 115 MB 00:14 ETA (10/52): kernel-debug-modules-4.10.8-100.fc24.x86_64.rpm | 23 MB 00:05
(11/52): kernel-debug-modu 57% [========= ] 5.8 MB/s | 116 MB 00:15 ETA (11/52): kernel-debug-modules-extra-4.10.8-100.fc24.x86_64 | 2.3 MB 00:00
(12/52): kernel-devel-4.10 58% [========= ] 5.8 MB/s | 119 MB 00:14 ETA (12/52): kernel-devel-4.10 59% [=========- ] 5.7 MB/s | 121 MB 00:14 ETA (12/52): kernel-devel-4.10 60% [=========- ] 5.8 MB/s | 123 MB 00:13 ETA (12/52): kernel-devel-4.10 61% [=========- ] 5.7 MB/s | 125 MB 00:13 ETA (12/52): kernel-devel-4.10 62% [=========- ] 5.8 MB/s | 127 MB 00:13 ETA (12/52): kernel-devel-4.10.8-100.fc24.x86_64.rpm | 11 MB 00:02
(13/52): kernel-headers-4.10.8-100.fc24.x86_64.rpm | 1.1 MB 00:00
(14/52): kernel-modules-4. 64% [========== ] 5.5 MB/s | 132 MB 00:13 ETA (14/52): kernel-modules-4. 65% [========== ] 5.5 MB/s | 133 MB 00:12 ETA (14/52): kernel-modules-4. 66% [==========- ] 5.6 MB/s | 135 MB 00:12 ETA (14/52): kernel-modules-4. 67% [==========- ] 5.6 MB/s | 137 MB 00:11 ETA (14/52): kernel-modules-4. 68% [==========- ] 5.6 MB/s | 139 MB 00:11 ETA (14/52): kernel-modules-4. 69% [=========== ] 5.6 MB/s | 141 MB 00:11 ETA (14/52): kernel-modules-4. 70% [=========== ] 5.6 MB/s | 143 MB 00:10 ETA (14/52): kernel-modules-4. 71% [=========== ] 5.7 MB/s | 146 MB 00:10 ETA (14/52): kernel-modules-4. 72% [===========- ] 5.7 MB/s | 147 MB 00:09 ETA (14/52): kernel-modules-4. 73% [===========- ] 5.7 MB/s | 150 MB 00:09 ETA (14/52): kernel-modules-4. 74% [===========- ] 5.8 MB/s | 151 MB 00:09 ETA (14/52): kernel-modules-4.10.8-100.fc24.x86_64.rpm | 23 MB 00:04
(15/52): kernel-modules-extra-4.10.8-100.fc24.x86_64.rpm | 2.2 MB 00:00
(16/52): kernel-tools-4.10.8-100.fc24.x86_64.rpm | 193 kB 00:00
(17/52): kernel-tools-libs-4.10.8-100.fc24.i686.rpm | 90 kB 00:00
(18/52): kernel-tools-libs-4.10.8-100.fc24.x86_64.rpm | 89 kB 00:00
(19/52): kernel-tools-libs-devel-4.10.8-100.fc24.i686.rpm | 83 kB 00:00
(20/52): kernel-tools-libs-devel-4.10.8-100.fc24.x86_64.rp | 83 kB 00:00
(21/52): pcs-0.9.156-2.fc2 77% [============ ] 5.1 MB/s | 157 MB 00:09 ETA (21/52): pcs-0.9.156-2.fc24.x86_64.rpm | 2.3 MB 00:00
(22/52): perf-4.10.8-100.fc24.x86_64.rpm | 1.7 MB 00:00
(23/52): perl-DateTime-Format-Flexible-0.28-1.fc24.noarch. | 50 kB 00:00
(24/52): perl-DateTime-TimeZone-2.01-8.fc24.noarch.rpm | 410 kB 00:00
(25/52): python-perf-4.10.8-100.fc24.x86_64.rpm | 182 kB 00:00
(26/52): python-sqlalchemy 79% [============- ] 4.9 MB/s | 162 MB 00:08 ETA (26/52): python-sqlalchemy-1.0.17-1.fc24.x86_64.rpm | 3.4 MB 00:00
(27/52): python-unbound-1.6.0-6.fc24.x86_64.rpm | 99 kB 00:00
(28/52): python3-3.5.3-4.fc24.i686.rpm | 57 kB 00:00
(29/52): python3-3.5.3-4.fc24.x86_64.rpm | 57 kB 00:00
(30/52): python3-debug-3.5.3-4.fc24.i686.rpm | 2.3 MB 00:00
(31/52): python3-debug-3.5 82% [============= ] 4.9 MB/s | 168 MB 00:07 ETA (31/52): python3-debug-3.5.3-4.fc24.x86_64.rpm | 2.5 MB 00:00
(32/52): python3-devel-3.5.3-4.fc24.i686.rpm | 203 kB 00:00
(33/52): python3-devel-3.5.3-4.fc24.x86_64.rpm | 203 kB 00:00
(34/52): python3-libs-3.5.3-4.fc24.i686.rpm | 1.4 MB 00:00
(35/52): python3-libs-3.5.3-4.fc24.x86_64.rpm | 1.4 MB 00:00
(36/52): python3-sqlalchem 85% [=============- ] 5.0 MB/s | 174 MB 00:06 ETA (36/52): python3-sqlalchemy-1.0.17-1.fc24.x86_64.rpm | 3.3 MB 00:00
(37/52): python3-test-3.5. 86% [=============- ] 5.1 MB/s | 177 MB 00:05 ETA (37/52): python3-test-3.5. 88% [============== ] 5.3 MB/s | 180 MB 00:04 ETA (37/52): python3-test-3.5.3-4.fc24.i686.rpm | 6.9 MB 00:00
(38/52): python3-test-3.5. 90% [============== ] 5.6 MB/s | 184 MB 00:03 ETA (38/52): python3-test-3.5. 92% [==============- ] 5.9 MB/s | 188 MB 00:02 ETA (38/52): python3-test-3.5.3-4.fc24.x86_64.rpm | 6.9 MB 00:00
(39/52): python3-tkinter-3.5.3-4.fc24.i686.rpm | 350 kB 00:00
(40/52): python3-tkinter-3.5.3-4.fc24.x86_64.rpm | 350 kB 00:00
(41/52): python3-tools-3.5.3-4.fc24.i686.rpm | 457 kB 00:00
(42/52): python3-tools-3.5.3-4.fc24.x86_64.rpm | 457 kB 00:00
(43/52): python3-unbound-1.6.0-6.fc24.x86_64.rpm | 101 kB 00:00
(44/52): system-python-3.5.3-4.fc24.x86_64.rpm | 51 kB 00:00
(45/52): system-python-lib 94% [=============== ] 5.8 MB/s | 193 MB 00:01 ETA (45/52): system-python-libs-3.5.3-4.fc24.i686.rpm | 6.3 MB 00:00
(46/52): system-python-lib 98% [===============-] 6.3 MB/s | 200 MB 00:00 ETA error: /var/www/html/repos/yum/fedora-updates-fc24/base/k/kernel-debug-devel-4.10.8-100.fc24.x86_64.rpm: headerRead failed: hdr load: BAD
(46/52): system-python-libs-3.5.3-4.fc24.x86_64.rpm | 6.3 MB 00:00
(47/52): unbound-1.6.0-6.fc24.x86_64.rpm | 638 kB 00:00
(48/52): unbound-devel-1.6.0-6.fc24.i686.rpm | 51 kB 00:00
(49/52): unbound-devel-1.6.0-6.fc24.x86_64.rpm | 51 kB 00:00
(50/52): unbound-libs-1.6.0-6.fc24.i686.rpm | 397 kB 00:00
(51/52): unbound-libs-1.6.0-6.fc24.x86_64.rpm | 397 kB 00:00
(52/52): unbound-munin-1.6.0-6.fc24.noarch.rpm | 33 kB 00:00
Removing kernel-debug-devel-4.10.8-100.fc24.x86_64.rpm due to failed signature check.
Build step 'Execute shell' marked build as failure
7 years, 8 months
oVirt repositories 101; or everything you wanted to know about oVirt repositories and didn't ask
by Eyal Edri
Hi oVirt developers and users,
Some of you might be familiar with the oVirt repositories and all their
flavors, while some of you are just familiar with the official releases.
The fact is, we have plenty of them and each has its own role and a right
usage. Moreover, we did a significant overhaul on all the repositories in
the past months,
So hopefully now it will be easier to explain which repo to use when.
I'll start with reviewing each oVirt repository and give a bit of
background and the logic behind it, how to consume it and the relevant
usage for it.
For simplicity, I'll review the repositories on the 4.1 release, but it
valid for all other oVirt releases ( except 'master' which doesn't have an
official or pre-release repositories ).
I will also upload this information to the oVirt.org site, but since this
is important, I didn't want to wait with the sending this email.
*oVirt repositories*
*Official repositories*
*Desc:* here you can find the official signed oVirt RPMs, immediately after
an official release has been done.
*Path:* http://resources.ovirt.org/pub/ovirt-4.1/rpm/$distro
*Update frequency:* on every oVirt release, usually happens on a monthly
cadence.
*Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm
*Who should use it? *
oVirt users, developers or anyone who wants a final and official release
*Pre-release repositories*
*Desc:* here you can find the pre-release bits of oVirt RC builds, just
before they are released.
*Path:* http://resources.ovirt.org/pub/ovirt-4.1-pre/rpm/$distro
*Update frequency:* usually on a weekly or bi-weekly basis
*Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-
release41-pre.rpm
*Who should use it? *
oVirt users, developers or anyone who wants to try out oVirt new version
before its out,
Keeping in mind this isn't a fully verified release and might still have
critical bugs which are not fixed yet.
Packages in this repo are verified by automation and checked by humans for
basic sanity before publishing.
*Nightly snapshot (verified) repositories*
*Desc:* here you can find the nightly snapshot of RPMs, which passed basic
sanity by our 'oVirt System Tests' framework in the oVirt CI system.
*Path:* http://resources.ovirt.org/pub/ovirt-4.1-snapshot/rpm/$distro
*Update frequency:* Every night
*Release rpm: *http://resources.ovirt.org/pub/yum-repo/ovirt-
release41-snapshot.rpm
*Who should use it? *
oVirt users, developers or anyone who wants to try out oVirt latest bits
right of the build oven!
We trust our system tests, which already run more than 40 various tests
such as 'add host', 'create VM', 'live migration' and more!
*** Important note: the snapshot repositories are verified only in master
currently, we might do the same for 4.1 soon, as we see no issues with
master so far ** *
*The above repos should suffice to most usres and developers, but if you
feel its not enough and you still need a faster verified repo, look below! *
*Advanced oVirt repositories*
*Builds artifacts repo*
*Desc:* This is a new feature from oVirt 'standard CI' project, where each
'build-artifacts' job is actually a yum repo as well.
*Path:* http://jenkins.ovirt.org/job/ovirt-engine_4.1_
build-artifacts-on-demand-el7-x86_64/lastSuccessfulBuild/
artifact/exported-artifacts ( example )
*Update frequency:* after each commit or 'ci please build' comment
*Release rpm: *N/A
*Who should use it? *
oVirt developers who need latest RPMs from another oVirt project and cannot
or need not wait for that project`s packages to pass OST".
oVirt developers running manual OST job and need to test an open Gerrit
patch, using the 'ci please build' command.
*Tested repositories*
*Desc:* The tested repositories hold all the oVIrt packages which passed CI
( similar to snapshot repos ) and retain also version history for X
versions back.
*Path:* http://resources.ovirt.org/repos/ovirt/tested/4.1/rpm/$distro
*Update frequency:* after each 'build artifacts' job is triggered by any
oVirt project and if the packages passed sanity checks
*Release rpm: *N/A
*Who should use it? *
If you want to have latest and greatest oVirt packages and can't wait for
the nightly repo.
If you are testing upgrades or need more than one version of a pacakge in
your repo.
*Experimental repositories *
*Desc:* Internal CI repos which are a part of the 'experimental' flow which
runs OST on each built package.
*Path:* http://resources.ovirt.org/repos/ovirt/experimental/
4.1/latest.tested/rpm/el7/$distro
*Update frequency:* after each 'build artifacts' job is triggered by any
oVirt project and if the packages passed sanity checks
*Release rpm: *N/A
*Who should use it? *
*No one other than internal CI jobs.*
These repos are constantly refreshed and RPMs are being removed from them,
so they are very prone to errors, please don't use them.
I hope this makes a bit of order in all the repos and how to use them.
If you still have questions, please don't hesitate to contact the infra
team at infra(a)ovirt.org or just reply to this thread.
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
7 years, 8 months
[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1312:
-----------------------------------
Summary: Make 'scan_for_artifacts.sh' publish repos separately
Key: OVIRT-1312
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Repositories Mgmt
Reporter: Barak Korren
Assignee: infra
The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions.
The issue is that if one of the repos fails to sync, the rest do not get synced either.
We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others.
--
This message was sent by Atlassian JIRA
(v1000.885.0#100040)
7 years, 8 months
[JIRA] (OVIRT-1312) Make 'scan_for_artifacts.sh' publish repos separately
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1312?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1312:
--------------------------------
Epic Link: OVIRT-403
> Make 'scan_for_artifacts.sh' publish repos separately
> -----------------------------------------------------
>
> Key: OVIRT-1312
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1312
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Repositories Mgmt
> Reporter: Barak Korren
> Assignee: infra
>
> The '{{scan_for_artifacts.sh}}' cron job runs on the resources server and syncs packages into the nightly snapshot repos. It tries to serially sync all repos for all oVirt versions.
> The issue is that if one of the repos fails to sync, the rest do not get synced either.
> We need to make the cron job sync each repo separately so failure mfor one repo will not affect the others.
--
This message was sent by Atlassian JIRA
(v1000.885.0#100040)
7 years, 8 months