- Infra - oVirt List Archives

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
by Martin Sivak (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] Martin Sivak commented on OVIRT-1299: ------------------------------------- The difference is that you depend on gerrit and on specific branch name to know which build-artifact script to execute. My requests does not require that, I will provide the git url and tarball url (or a dir with those) instead. Something very similar to what I want is the releng tools repository Sandro uses. An example: https://gerrit.ovirt.org/gitweb?p=releng-tools.git;a=blob;f=releases/ovirt-… The only issue we have with this is that it is not properly documented (inheritance rules, ...), does not support source tarballs and CI is probably not using it at all. > Please provide a koji (and if possible bodhi) instance for ovirt repositories > ----------------------------------------------------------------------------- > > Key: OVIRT-1299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > Some of the maintainers of oVirt project wants to have control on the builds going into the release repositories without 3rd party intervention on it. > They would like to have a dist-git + koji like developer experience. > A bodhi instance would help reviewing the package before it lands on repositories. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #288
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Eyal Edri] drop qmeu master merged job ------------------------------------------ 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 c7f97c6100e0a53f679bd711bf05ca8f6a89a6a0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c7f97c6100e0a53f679bd711bf05ca8f6a89a6a0 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/hudson4269871197106904657.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 if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 912, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1299) Please provide a koji (and if possible bodhi) instance for ovirt repositories
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1299: ------------------------------------- I'm not sure I understand the process, and how it differs from what we have now. A "build-artifacts" job can build in any way the developer chooses, including invoking remote build services. As long as it eventually leaves RPMs in exported-artifacts, they will be taken, system-tested and published. Every 'build-artifacts' job is also a package repository so you even get publishing "for free" without passing OST. If you want to separate the build/release process from source that is also easy to do, you just create a separate repo, place build scripts in it, and make them clone the "source" repo. This is essentially what the UX team did for various 3rd party dependencies. We will probably not further automate the use of specific build systems, nor is it probable that we will deploy any new build system. WRT GitHub - using it does not imply using a different process, we've been running a very oVirt-like process on GitHub for Lago for quite a long while now. And we've recently started doing this for other projects as well. > Please provide a koji (and if possible bodhi) instance for ovirt repositories > ----------------------------------------------------------------------------- > > Key: OVIRT-1299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1299 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > Some of the maintainers of oVirt project wants to have control on the builds going into the release repositories without 3rd party intervention on it. > They would like to have a dist-git + koji like developer experience. > A bodhi instance would help reviewing the package before it lands on repositories. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #219
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/219/displa…> Changes: [Eyal Edri] drop qmeu master merged job ------------------------------------------ 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-epel-el6-x86_64/ws/> > 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 c7f97c6100e0a53f679bd711bf05ca8f6a89a6a0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c7f97c6100e0a53f679bd711bf05ca8f6a89a6a0 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson1605555710363075578.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: epel-el6 Syncing yum repo epel-el6 for arch: x86_64 : php-horde-horde-5.2.14-1.el6.noarch.rpm | 1.6 MB 00:01 Removing php-horde-Horde-Image-2.4.0-1.el6.noarch.rpm due to failed signature check. Removing php-horde-horde-5.2.14-1.el6.noarch.rpm due to failed signature check. Removing php-horde-imp-6.2.18-1.el6.noarch.rpm due to failed signature check. Removing php-horde-kronolith-4.2.20-1.el6.noarch.rpm due to failed signature check. Removing php-horde-mnemo-4.2.13-1.el6.noarch.rpm due to failed signature check. Removing php-horde-nag-4.2.14-1.el6.noarch.rpm due to failed signature check. Removing php-horde-turba-4.2.19-1.el6.noarch.rpm due to failed signature check. Removing rhash-1.3.4-2.el6.i686.rpm due to failed signature check. Removing rhash-1.3.4-2.el6.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1300) Jenkins jobs stuck on mock init/scrub
by Evgheni Dereveanchin (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1300?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1300: ------------------------------------------- Assignee: Barak Korren (was: infra) > Jenkins jobs stuck on mock init/scrub > ------------------------------------- > > Key: OVIRT-1300 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1300 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Barak Korren > Priority: High > > There's several dozen check-patch jobs currently stuck on the Jenkins Master with the last line related to mock: > 09:44:22 ========== Scrubbing chroot > 09:44:22 mock \ > 09:44:22 --configdir="/home/jenkins/workspace/ovirt-engine_master_check-patch-el7-x86_64/ovirt-engine" \ > 09:44:22 --root="mocker-epel-7-x86_64.el7" \ > 09:44:22 --resultdir="./mock_logs.I6ufSyEH/mocker-epel-7-x86_64.el7.scrub" \ > 09:44:22 --scrub=chroot > This needs to be fixed. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1181 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

------=_Part_211_1899481957.1491382771814 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1181/, Build Number: 1181, Build Status: FAILURE ------=_Part_211_1899481957.1491382771814--

1 1

[JIRA] (OVIRT-1301) Add timeouts to mirror client
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1301?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1301: ----------------------------------- Assignee: Barak Korren (was: infra) > Add timeouts to mirror client > ----------------------------- > > Key: OVIRT-1301 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1301 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > It seems that the mirror client can get stuck forever if the mirror server responds slowly, or not at all. > We need to ad a time out to fall back to not using the mirrors. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1301) Add timeouts to mirror client
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1301?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1301: -------------------------------- Epic Link: OVIRT-403 > Add timeouts to mirror client > ----------------------------- > > Key: OVIRT-1301 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1301 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > It seems that the mirror client can get stuck forever if the mirror server responds slowly, or not at all. > We need to ad a time out to fall back to not using the mirrors. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1301) Add timeouts to mirror client
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

Barak Korren created OVIRT-1301: ----------------------------------- Summary: Add timeouts to mirror client Key: OVIRT-1301 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1301 Project: oVirt - virtualization made easy Issue Type: Bug Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High It seems that the mirror client can get stuck forever if the mirror server responds slowly, or not at all. We need to ad a time out to fall back to not using the mirrors. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1300) Jenkins jobs stuck on mock init/scrub
by Evgheni Dereveanchin (oVirt JIRA) 05 Apr '17

05 Apr '17

Evgheni Dereveanchin created OVIRT-1300: ------------------------------------------- Summary: Jenkins jobs stuck on mock init/scrub Key: OVIRT-1300 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1300 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: High There's several dozen check-patch jobs currently stuck on the Jenkins Master with the last line related to mock: 09:44:22 ========== Scrubbing chroot 09:44:22 mock \ 09:44:22 --configdir="/home/jenkins/workspace/ovirt-engine_master_check-patch-el7-x86_64/ovirt-engine" \ 09:44:22 --root="mocker-epel-7-x86_64.el7" \ 09:44:22 --resultdir="./mock_logs.I6ufSyEH/mocker-epel-7-x86_64.el7.scrub" \ 09:44:22 --scrub=chroot This needs to be fixed. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0