- Infra - oVirt List Archives

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

05 Apr '17

------=_Part_247_914655397.1491419877676 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6212/, Build Number: 6212, Build Status: FAILURE ------=_Part_247_914655397.1491419877676--

1 1

Duplicate user in gerrit
by Ori Liel 05 Apr '17

05 Apr '17

Hi, I was informed that there's a problem adding me as a reviewer in gerrit, since my user is duplicated. Can you please help me with this? Thanks, Ori.

2 2

[JIRA] (OVIRT-1294) oliel - Duplicate user in gerrit
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1294?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1294: -------------------------------- Blocked By: Blocking on contacting user to verify fix Status: Blocked (was: To Do) > oliel - Duplicate user in gerrit > -------------------------------- > > Key: OVIRT-1294 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1294 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Barak Korren > > Forwarding to infra-support to open a ticket. > ---------- Forwarded message ---------- > From: Ori Liel <oliel(a)redhat.com> > Date: 3 April 2017 at 08:34 > Subject: Duplicate user in gerrit > To: infra <infra(a)ovirt.org> > Hi, > I was informed that there's a problem adding me as a reviewer in > gerrit, since my user is duplicated. > Can you please help me with this? > Thanks, > Ori. > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

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

05 Apr '17

------=_Part_215_1852687810.1491384212001 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6202/, Build Number: 6202, Build Status: FAILURE ------=_Part_215_1852687810.1491384212001--

1 9

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

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1299: ----------------------------------------- +1 for ovirt-web-ui, we're going to use the same flow > 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

[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: ------------------------------------- Exactly what I would like to achieve. With one improvement in step 3. I usually release in the same copr repo so in the ideal world I would just provide the repo url once and every time you do a compose (or nightly) the tooling would check for updates. > 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

[JIRA] (OVIRT-1302) Please merge my multiple gerrit identies
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1302?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1302: ----------------------------------- Assignee: Barak Korren (was: infra) > Please merge my multiple gerrit identies > ---------------------------------------- > > Key: OVIRT-1302 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1302 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: vfeenstr > Assignee: Barak Korren > > I added new auth methods (Github and Gmail) and now I can't be assigned anymore by others to reviews etc. > vfeenstr @ RH -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[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: ------------------------------------- {quote} 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. {quote} It does not have to be in Gerrit, nor is there a need for specific branches ATM. The discussion about branches was trying to come up with a scheme to auto-detect things that are currently specified in the project YAML in the Jenkins repo. Since we did not implement that yet, you can use any branch names you'd like and map them to oVirt releases in the YAML file. The one thing we do strongly depend on, is that every change starts with a commit somewhere so that we can track it, and use the hash as a reliable unique identifier for the change. I think this is important. Without it you cannot track changes. {quote} 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. {quote} That is a repoman configuration file. All it does is collect files together. This is not a reliable source of information, not is it located in the right place, because AFAIK deciding which package builds go to which oVirt releases is the responsibility of the individual package maintainers, not the integration team. But still, I'm not sure I understand where you are trying to go. Let me try to describe the process you are tying to get to as I understand it: # You merge a new commit to mom # You go and launch a build in copr manually. # When the build is done you go to some file in some repo, specify the url to the build in it and submit a new commit. # Once the new commit is merged the CY system downloads the new build and publishes it in the oVirt repos. > 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

[JIRA] (OVIRT-1302) Please merge my multiple gerrit identies
by vfeenstr (oVirt JIRA) 05 Apr '17

05 Apr '17

vfeenstr created OVIRT-1302: ------------------------------- Summary: Please merge my multiple gerrit identies Key: OVIRT-1302 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1302 Project: oVirt - virtualization made easy Issue Type: Task Reporter: vfeenstr Assignee: infra I added new auth methods (Github and Gmail) and now I can't be assigned anymore by others to reviews etc. vfeenstr @ RH -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[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

[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 edited comment on OVIRT-1299 at 4/5/17 1:00 PM: ------------------------------------------------------------- Do not make this more complex than it has to be. A simple text or ini file (in ovirt specific repository, not in the project itself!) where the maintainer can say which build (a link to jenkins, copr, koji, github, ...) should go to which release is enough. The same for source tarball. Just let us provide a link (git hash url, gitweb export or github for example). All your tooling like publishers or CI or anything else can then consume this configuration without forcing us to use a fixed tag or branch structure. The maintainer should be in control of the releases or platform, not the automation. oVirt is a distribution of pieces and some pieces have slightly different development model. Even some core oVirt project use GitHub as the primary source now. This has been discussed couple of times already, for example here http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here http://lists.ovirt.org/pipermail/devel/2017-January/029161.html was (Author: msivak(a)redhat.com) Do not make this more complex than it has to be. A simple text or ini file where the maintainer can say which build (a link to jenkins, copr, koji, github, ...) should go to which release is enough. The same for source tarball. Just let us provide a link (git hash url, gitweb export or github for example). All your tooling like publishers or CI or anything else can then consume this configuration without forcing us to use a fixed tag or branch structure. The maintainer should be in control of the releases or platform, not the automation. oVirt is a distribution of pieces and some pieces have slightly different development model. Even some core oVirt project use GitHub as the primary source now. This has been discussed couple of times already, for example here http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here http://lists.ovirt.org/pipermail/devel/2017-January/029161.html > 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

[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: ------------------------------------- Do not make this more complex than it has to be. A simple text or ini file where the maintainer can say which build (a link to jenkins, copr, koji, github, ...) should go to which release is enough. The same for source tarball. Just let us provide a link (git hash url, gitweb export or github for example). All your tooling like publishers or CI or anything else can then consume this configuration without forcing us to use a fixed tag or branch structure. The maintainer should be in control of the releases or platform, not the automation. oVirt is a distribution of pieces and some pieces have slightly different development model. Even some core oVirt project use GitHub as the primary source now. This has been discussed couple of times already, for example here http://lists.ovirt.org/pipermail/devel/2017-February/029439.html and here http://lists.ovirt.org/pipermail/devel/2017-January/029161.html > 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

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

05 Apr '17

sbonazzo created OVIRT-1299: ------------------------------- Summary: 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

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

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1299?page=com.atlassian.jira.… ] sbonazzo updated OVIRT-1299: ---------------------------- Epic Link: OVIRT-411 > 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

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6201 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

------=_Part_209_779165259.1491381851774 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6201/, Build Number: 6201, Build Status: SUCCESS ------=_Part_209_779165259.1491381851774--

1 0

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

05 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el7-x86_64/214/displa…> ------------------------------------------ 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-el7-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 bdca0b5702e3f2058805edcff168947ee95b1996 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bdca0b5702e3f2058805edcff168947ee95b1996 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-epel-el7-x86_64] $ /bin/bash -xe /tmp/hudson6785463584392011933.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: epel-el7 Syncing yum repo epel-el7 for arch: x86_64 (2/18): check-mk-agent-1.2 0% [ ] 0.0 B/s | 0 B --:-- ETA check-mk-1.2.8p18-1.el7.x86_64 FAILED (2/18): check-mk-agent-1.2 0% [ ] 0.0 B/s | 0 B --:-- ETA check-mk-multisite-1.2.8p18-1. FAILED (2/18): check-mk-docs-1.2. 0% [ ] 0.0 B/s | 0 B --:-- ETA python2-fedmsg-atomic-composer FAILED (2/18): check-mk-docs-1.2. 0% [ ] 0.0 B/s | 0 B --:-- ETA gasnet-common-1.28.2-1.el7.x86 FAILED (2/18): check-mk-docs-1.2. 0% [ ] 0.0 B/s | 0 B --:-- ETA check-mk-agent-1.2.8p18-1.el7. FAILED (2/18): check-mk-docs-1.2. 0% [ ] 0.0 B/s | 0 B --:-- ETA (2/18): check-mk-livestatu 4% [- ] 0.0 B/s | 799 kB --:-- ETA (1/18): check-mk-livestatus-1.2.8p18-1.el7.x86_64.rpm | 222 kB 00:00 gasnet-common-1.28.2-1.el7.x86 FAILED (3/18): distribution-gpg-k 4% [- ] 0.0 B/s | 799 kB --:-- ETA (2/18): check-mk-docs-1.2.8p18-1.el7.noarch.rpm | 1.6 MB 00:01 (3/18): perl-Test-TCP-2.17-2.el7.noarch.rpm | 29 kB 00:00 (4/18): distribution-gpg-keys-1.10-1.el7.noarch.rpm | 126 kB 00:00 (5/18): gasnet-mpich-1.28.2-1.el7.x86_64.rpm | 1.0 MB 00:01 (6/18): check-mk-agent-1.2.8p18-1.el7.x86_64.rpm | 89 kB 00:00 (7/18): gasnet-common-1.28.2-1.el7.x86_64.rpm | 15 kB 00:00 (9/18): gasnet-1.28.2-1.el 20% [=== ] 4.4 MB/s | 3.5 MB 00:03 ETA (8/18): python34-scripttest-1.3.0-9.el7.noarch.rpm | 101 kB 00:00 (9/18): gasnet-openmpi-1.28.2-1.el7.x86_64.rpm | 1.0 MB 00:01 (10/18): python2-scripttest-1.3.0-9.el7.noarch.rpm | 101 kB 00:00 (11/18): reposurgeon-3.42-1.el7.noarch.rpm | 275 kB 00:01 (12/18): gasnet-1.28.2-1.el7.x86_64.rpm | 828 kB 00:01 (13/18): gasnet-devel-1.28.2-1.el7.x86_64.rpm | 194 kB 00:01 (15/18): gasnet-doc-1.28.2 56% [========= ] 5.3 MB/s | 9.5 MB 00:01 ETA (14/18): check-mk-multisite-1.2.8p18-1.el7.noarch.rpm | 3.5 MB 00:00 (15/18): distribution-gpg-keys-copr-1.10-1.el7.noarch.rpm | 6.1 MB 00:01 (16/18): check-mk-1.2.8p18-1.el7.x86_64.rpm | 1.1 MB 00:01 (17/18): python2-fedmsg-atomic-composer-2017.1-1.el7.noarc | 35 kB 00:00 (18/18): gasnet-doc-1.28.2-1.el7.noarch.rpm | 525 kB 00:01 Generating yum repo metadata for: epel-el7 Worker 0: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/c/check-mk-1.2.8p18-1.el7.x86_64.rpm: RPM Error opening Package Worker 0: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/p/python34-scripttest-1.3.0-9.el7.noarch.rpm: RPM Error opening Package Worker 1: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/c/check-mk-agent-1.2.8p18-1.el7.x86_64.rpm: RPM Error opening Package Worker 1: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/g/gasnet-devel-1.28.2-1.el7.x86_64.rpm: RPM Error opening Package Worker 1: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/r/reposurgeon-3.42-1.el7.noarch.rpm: RPM Error opening Package Worker 2: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/c/check-mk-docs-1.2.8p18-1.el7.noarch.rpm: RPM Error opening Package Worker 2: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/g/gasnet-doc-1.28.2-1.el7.noarch.rpm: RPM Error opening Package Worker 4: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/c/check-mk-multisite-1.2.8p18-1.el7.noarch.rpm: RPM Error opening Package Worker 4: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/g/gasnet-openmpi-1.28.2-1.el7.x86_64.rpm: RPM Error opening Package Worker 5: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/d/distribution-gpg-keys-1.10-1.el7.noarch.rpm: RPM Error opening Package Worker 6: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/d/distribution-gpg-keys-copr-1.10-1.el7.noarch.rpm: RPM Error opening Package Worker 7: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/g/gasnet-1.28.2-1.el7.x86_64.rpm: RPM Error opening Package Worker 7: Error: Could not open local rpm file: /var/www/html/repos/yum/epel-el7/base/p/python2-scripttest-1.3.0-9.el7.noarch.rpm: RPM Error opening Package Failed to process 13 package(s). Spawning worker 0 with 3 pkgs Spawning worker 1 with 3 pkgs Spawning worker 2 with 2 pkgs Spawning worker 3 with 2 pkgs Spawning worker 4 with 2 pkgs Spawning worker 5 with 2 pkgs Spawning worker 6 with 2 pkgs Spawning worker 7 with 2 pkgs Workers Finished Build step 'Execute shell' marked build as failure

1 2

[JIRA] (OVIRT-1298) Mirrors sync jobs started to fail b/c of failed package signatures
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1298?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1298: ----------------------------------- Assignee: Barak Korren (was: infra) > Mirrors sync jobs started to fail b/c of failed package signatures > ------------------------------------------------------------------ > > Key: OVIRT-1298 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1298 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > This is happening for Fedora and EPEL repos, so probably the fedora signing keys were changed, and need to to be updated on the mirrors host. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1298) Mirrors sync jobs started to fail b/c of failed package signatures
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

Barak Korren created OVIRT-1298: ----------------------------------- Summary: Mirrors sync jobs started to fail b/c of failed package signatures Key: OVIRT-1298 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1298 Project: oVirt - virtualization made easy Issue Type: Bug Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High This is happening for Fedora and EPEL repos, so probably the fedora signing keys were changed, and need to to be updated on the mirrors host. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1298) Mirrors sync jobs started to fail b/c of failed package signatures
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1298?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1298: -------------------------------- Epic Link: OVIRT-403 > Mirrors sync jobs started to fail b/c of failed package signatures > ------------------------------------------------------------------ > > Key: OVIRT-1298 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1298 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > This is happening for Fedora and EPEL repos, so probably the fedora signing keys were changed, and need to to be updated on the mirrors host. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by Barak Korren (oVirt JIRA) 05 Apr '17

05 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1296?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1296: ------------------------------------- Using 'Rebase Always' will have indeed allowd us to meet some user's requests. But it has the downside where you will never be able to fast-forward over your own local commits because the merged commits will always be different then the submitted ones. Still, worth publishing to devel and seeing if anyone wants to try this in his project. BTW I seem to remember I already saw it as an option somewhere, was I looking at the staging instance? > review Rebase Always submit strategy on Gerrit > ---------------------------------------------- > > Key: OVIRT-1296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Lowest > > A new submit strategy was included in recent builds of Gerrit: Rebase Always. > [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] > {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. > Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} > It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc25-x86_64 #143
by jenkins＠jenkins.phx.ovirt.org 05 Apr '17

05 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc25-x86_64…> ------------------------------------------ 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-fc25-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 bdca0b5702e3f2058805edcff168947ee95b1996 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bdca0b5702e3f2058805edcff168947ee95b1996 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-fedora-updates-fc25-x86_64] $ /bin/bash -xe /tmp/hudson4703658036041167474.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc25 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: fedora-updates-fc25 Syncing yum repo fedora-updates-fc25 for arch: x86_64 fedora-updates-fc25/presto 0% [ ] 0.0 B/s | 0 B --:-- ETA fedora-updates-fc25/presto 37% [====== ] 0.0 B/s | 769 kB --:-- ETA fedora-updates-fc25/prestodelta | 2.0 MB 00:00 : rsync-bpc-3.0.9.5-2.fc25.x86_64.rpm | 263 kB 00:00 Generating yum repo metadata for: fedora-updates-fc25 Worker 2: Error: Could not open local rpm file: /var/www/html/repos/yum/fedora-updates-fc25/base/p/python-perf-4.10.8-200.fc25.x86_64.rpm: RPM Error opening Package Worker 3: Error: Could not open local rpm file: /var/www/html/repos/yum/fedora-updates-fc25/base/p/python-sqlalchemy-1.0.17-1.fc25.x86_64.rpm: RPM Error opening Package Worker 4: Error: Could not open local rpm file: /var/www/html/repos/yum/fedora-updates-fc25/base/p/pcs-0.9.156-2.fc25.x86_64.rpm: RPM Error opening Package Worker 6: Error: Could not open local rpm file: /var/www/html/repos/yum/fedora-updates-fc25/base/p/python3-sqlalchemy-1.0.17-1.fc25.x86_64.rpm: RPM Error opening Package Worker 7: Error: Could not open local rpm file: /var/www/html/repos/yum/fedora-updates-fc25/base/r/rsync-bpc-3.0.9.5-2.fc25.x86_64.rpm: RPM Error opening Package Failed to process 5 package(s). Spawning worker 0 with 6 pkgs Spawning worker 1 with 6 pkgs Spawning worker 2 with 6 pkgs Spawning worker 3 with 6 pkgs Spawning worker 4 with 6 pkgs Spawning worker 5 with 6 pkgs Spawning worker 6 with 6 pkgs Spawning worker 7 with 6 pkgs Workers Finished Build step 'Execute shell' marked build as failure

1 3

[JIRA] (OVIRT-1297) _manual flavor for ovirt_master_hc-system-tests
by danken (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1297?page=com.atlassian.jira.… ] danken updated OVIRT-1297: -------------------------- Resolution: Fixed Status: Done (was: To Do) I was not aware of SUITE_TYPE > _manual flavor for ovirt_master_hc-system-tests > ----------------------------------------------- > > Key: OVIRT-1297 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1297 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: danken > Assignee: infra > > recently we broke ovirt_master_hc-system-tests. > we would like to verify whether https://gerrit.ovirt.org/#/c/75134/ fixes it. > having ovirt_master_hc-system-tests_manual could have helped a lot. -- This message was sent by Atlassian JIRA (v1000.883.0#100040)

1 0

oVirt infra daily report - unstable production jobs - 281
by jenkins＠jenkins.phx.ovirt.org 04 Apr '17

04 Apr '17

------=_Part_195_702766108.1491346825744 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/281//artifact/exported-a… Cheers, Jenkins ------=_Part_195_702766108.1491346825744 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 04/04/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el7-x86_64/">system-sync_mirrors-epel-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc24-x86_64/">system-sync_mirrors-fedora-updates-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc25-x86_64/">system-sync_mirrors-fedora-updates-fc25-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_195_702766108.1491346825744--

1 0

[JIRA] (OVIRT-1297) _manual flavor for ovirt_master_hc-system-tests
by danken (oVirt JIRA) 04 Apr '17

04 Apr '17

danken created OVIRT-1297: ----------------------------- Summary: _manual flavor for ovirt_master_hc-system-tests Key: OVIRT-1297 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1297 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: danken Assignee: infra recently we broke ovirt_master_hc-system-tests. we would like to verify whether https://gerrit.ovirt.org/#/c/75134/ fixes it. having ovirt_master_hc-system-tests_manual could have helped a lot. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1296) review Rebase Always submit strategy on Gerrit
by Evgheni Dereveanchin (oVirt JIRA) 04 Apr '17

04 Apr '17

Evgheni Dereveanchin created OVIRT-1296: ------------------------------------------- Summary: review Rebase Always submit strategy on Gerrit Key: OVIRT-1296 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1296 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Lowest A new submit strategy was included in recent builds of Gerrit: Rebase Always. [Docs|https://gerrit-review.googlesource.com/Documentation/project-configura…] {quote}Basically, the same as Rebase If Necessary, but it creates a new patchset even if fast forward is possible AND like Cherry Pick it ensures footers such as Change-Id, Reviewed-On, and others are present in resulting commit that is merged. Thus, Rebase Always can be considered similar to Cherry Pick, but with the important distinction that Rebase Always does not ignore dependencies.{quote} It is only available in [2.14|https://gerrit.googlesource.com/gerrit/+/stable-2.14/gerrit-server/src…] while we are still at 2.12 and [2.13|https://gerrit.googlesource.com/gerrit/+/stable-2.13/gerrit-server/src…] is the current stable branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1250: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: Daniel Belenky > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Michal Skrivanek (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1250: ----------------------------------------- any progress? example of a message every 2 hours: https://github.com/oVirt/ovirt-web-ui/pull/113 > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Barak Korren (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1295: ------------------------------------- [~ykaul] To run OST, you need to automatically come up with a proper merging order, and then emulate the sequence of merges. Then you need to also build the artifacts, and only then you can start considering running OST. And you need to do all this for engine, vdsm, and probably other projects as well. And when OST fails, you also want to narrow down the failure to the specific patch that caused it. This is what we call "gating" or "patch-queueing" our currently ongoing "package gating" or "change queue" work (OVIRT-1077) is a necessary predecessor to that. > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Yaniv Kaul (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Yaniv Kaul commented on OVIRT-1295: ----------------------------------- I think we need to see how many of those we have - and how many have CR+1 and V+1 and can go through the same process as well - on lower priority (say, on 3AM in the morning). What about running o-s-t on the first batch? > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

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

04 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/215/displa…> ------------------------------------------ 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 bdca0b5702e3f2058805edcff168947ee95b1996 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bdca0b5702e3f2058805edcff168947ee95b1996 > git rev-list bdca0b5702e3f2058805edcff168947ee95b1996 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson7434573794514853450.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 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 687, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, 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 96, in retrieveAllMD downloading = repo._commonRetrieveDataMD_list(mdtypes) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1590, in _commonRetrieveDataMD_list os.rename(local, local + '.old.tmp') OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by eyal edri [Administrator] (oVirt JIRA) 04 Apr '17

04 Apr '17

eyal edri [Administrator] created OVIRT-1295: ------------------------------------------------ Summary: Add job to auto-rebase patches that are ready to be merged Key: OVIRT-1295 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by eyal edri [Administrator] (oVirt JIRA) 04 Apr '17

04 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1295: --------------------------------------------- Epic Link: OVIRT-403 > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian JIRA (v1000.870.5#100039)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc25-x86_64 #141
by jenkins＠jenkins.phx.ovirt.org 04 Apr '17

04 Apr '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc25-x86_64/14…> ------------------------------------------ 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-base-fc25-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 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128: stdout: stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': The requested URL returned error: 503 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1784) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1513) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to mirrors.phx.ovirt.org(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor473.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy72.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) ... 11 more ERROR: null

1 1

planned Gerrit maintenance
by Evgheni Dereveanchin 03 Apr '17

03 Apr '17

Hi everyone, I will be performing updates on gerrit.ovirt.org during the next hour. Within this period the UI and repositories may be unavailable. I will follow up as soon as maintenance activities are over. -- Regards, Evgheni Dereveanchin

1 1

oVirt infra daily report - unstable production jobs - 280
by jenkins＠jenkins.phx.ovirt.org 03 Apr '17

03 Apr '17

------=_Part_180_1309132941.1491260418579 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/280//artifact/exported-a… Cheers, Jenkins ------=_Part_180_1309132941.1491260418579 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 03/04/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc25-x86_64/">system-sync_mirrors-fedora-base-fc25-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_180_1309132941.1491260418579--

1 0

[ OST Failure Report ] [ oVirt master ] [ 3/4/2017 ] [test_intialize_engine]
by Barak Korren 03 Apr '17

03 Apr '17

Link to suspected patches: https://gerrit.ovirt.org/#/c/73688/ Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/artif… Error snippet from log: <error> [ INFO ] Starting engine service [ ERROR ] Failed to execute stage 'Closing up': Failed to start service 'ovirt-engine' [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20170403084130-sfzp94.log </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/Test failed: [ TEST NAME ]

2 1

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

03 Apr '17

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

1 2

Re: [ovirt-devel] GUI error on master: Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError)
by Nadav Goldin 03 Apr '17

03 Apr '17

> Any chance you can install them and retry? > sudo yum install ovirt-engine-webadmin-portal-debuginfo Surprisingly OST didn't pull it. I see it is listed in the reposync config under the 'ovirt-master-snapshot-static', but I think its not there any more. Is it built like all other packages consumed in the experimental flow? On Sun, Apr 2, 2017 at 4:00 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > > On Sun, Apr 2, 2017 at 3:18 PM, Greg Sheremeta <gshereme(a)redhat.com> wrote: >> >> """ >> GWT symbolmaps are not installed, please install >> them to de-obfuscate the UI stack traces >> 2017-04-02 06:12:25,980-04 ERROR >> """ >> >> Any chance you can install them and retry? >> sudo yum install ovirt-engine-webadmin-portal-debuginfo > > > && sudo systemctl restart ovirt-engine > > Y. > >> >> >> >> On Sun, Apr 2, 2017 at 6:25 AM, Nadav Goldin <ngoldin(a)redhat.com> wrote: >>> >>> Hi, >>> Running OST basic-suite-master and logging to the GUI, appears a >>> warning pop-up window: >>> Uncaught exception occurred. Please try reloading the page. Details: >>> (TypeError) : a.i is undefined >>> Please have your administrator check the UI logs >>> >>> ui.log: >>> 2017-04-02 06:12:25,975-04 INFO >>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] >>> (default task-3) [] GWT symbolmaps are not installed, please install >>> them to de-obfuscate the UI stack traces >>> 2017-04-02 06:12:25,980-04 ERROR >>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] >>> (default task-3) [] Permutation name: E0637AA26393B2D56C4B42EFB5EA0C00 >>> 2017-04-02 06:12:25,980-04 ERROR >>> [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] >>> (default task-3) [] Uncaught exception: >>> com.google.gwt.core.client.JavaScriptException: (TypeError) : a.i is >>> undefined >>> at >>> Unknown.itp(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.Btp(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.pWo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.sWo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.JYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.MYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.jYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.mYo(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.PPe(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.E_(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.T_(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.onreadystatechange<(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.Bu(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.Eu(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at >>> Unknown.Du/<(https://192.168.201.3/ovirt-engine/webadmin/?locale=en_US#dashboard-main) >>> at Unknown.anonymous(Unknown) >>> >>> >>> engine version: 4.2.0-0.0.master.20170402071029.git17ebf70.el7.centos >>> firefox: firefox-52.0-7.fc25.x86_64 >>> >>> Off hand, everything looks functional. >>> >>> >>> >>> Thanks, >>> >>> Nadav. >>> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >> >> >> >> >> -- >> Greg Sheremeta, MBA >> Red Hat, Inc. >> Sr. Software Engineer >> gshereme(a)redhat.com >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > >

3 5

[ OST Failure Report ] [ oVirt 4.1 ] [ 3/4/2017 ] [test_initialize_engine]
by Barak Korren 03 Apr '17

03 Apr '17

Test failed: test_initialize_engine Link to suspected patches: https://gerrit.ovirt.org/75054 Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1162/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1162/artifact… Error snippet from log: <error> 2017-04-03 10:16:48 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/bin/systemctl', 'start', 'ovirt-engine.service') stderr: Job for ovirt-engine.service failed because the control process exited with error code. See "systemctl status ovirt-engine.service" and "journalctl -xe" for details. 2017-04-03 10:16:48 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 57, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'ovirt-engine' </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6164 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Apr '17

03 Apr '17

------=_Part_161_570839099.1491223570612 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6164/, Build Number: 6164, Build Status: FAILURE ------=_Part_161_570839099.1491223570612--

1 5

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6161 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Apr '17

03 Apr '17

------=_Part_157_446119441.1491213078993 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/6161/, Build Number: 6161, Build Status: FAILURE ------=_Part_157_446119441.1491213078993--

1 1