February 2018 - Infra - oVirt List Archives

oVirt infra weekly meeting notes 14.02.2018
by Evgheni Dereveanchin 15 Feb '18

15 Feb '18

Hi everyone, Please find the topics of this week's infra meeting below: PHX DC: - oVirt 4.2.1 is out - infra update due - ManageIQ re-deployed using Ansible: https://staging-manageiq.phx.ovirt.org/ - Monitoring alerts for resources - slowness due to release - oVirt volume provisioning for OpenShift, staging-shift runs on local storage DCs AI: - Link ManageIQ to OpenShift - Add ManageIQ to Puppet - done - Document user management and check if external auth is possible: http://manageiq.org/docs/reference/latest/auth/saml -- Regards, Evgheni Dereveanchin

1 0

Would like to become infra volunteer for ovirt project
by Sahil Joseph 14 Feb '18

14 Feb '18

Hi everyone, This is Sahil I would like to volunteer to manage infra for ovirt project. Can any one mentor me and tell me where to start. Regards Sahil

2 1

[CQ]: 87594, 1 (ovirt-engine-sdk-java) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Feb '18

14 Feb '18

Change 87594,1 (ovirt-engine-sdk-java) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/87594/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/791/

1 0

Do the CI support creating a github releases + assets?
by Roy Golan 14 Feb '18

14 Feb '18

I'm currently rolling my own makefile to create a release, with a binary file as assets. Does standard CI have something to publish artifacts in GH releases?

2 3

[oVirt CI] standard-enqueue - Build #10125 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 14 Feb '18

14 Feb '18

------=_Part_234_1331611098.1518608050920 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/10125/ Build Name: #10125 Build Description: Gerrit: 87594 - ovirt-engine-sdk-java (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/87594 - title: packaging: add support for newest fedoras - project: ovirt-engine-sdk-java - branch: sdk_3.6 - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_234_1331611098.1518608050920--

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1196
by jenkins＠jenkins.phx.ovirt.org 14 Feb '18

14 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1196/displ…> ------------------------------------------ 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 633e9a8b0cddbe18f68cd295f21a60e6675558be (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 633e9a8b0cddbe18f68cd295f21a60e6675558be Commit message: "ovirt-host: drop s390x fcraw jobs" > git rev-list 633e9a8b0cddbe18f68cd295f21a60e6675558be # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins5013792939690223846.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 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

This is a multi-part message in MIME format... ------------=_1518592373-16157-109 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1895: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518592373-16157-109 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1895:</h3> <pre>Resolution: Duplicate Status: Done (was: To Do)</pre> <blockquote><h3>CI votes not forwarded on commit message change</h3> <pre> Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, If a change goes through this flow:</p> <ol><li><p>Push an update N</p></li> <li><p>CI triggers check-patch for N</p></li> <li><p>Push another update N+1 that changes only commit message</p></li> <li><p>CI marks +1 N</p></li></ol> <p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518592373-16157-109--

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

This is a multi-part message in MIME format... ------------=_1518592365-27516-116 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1895: -------------------------------- Component/s: Gerrit/git Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL) > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518592365-27516-116 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1895:</h3> <pre>Component/s: Gerrit/git Epic Link: OVIRT-400 Issue Type: Bug (was: By-EMAIL)</pre> <blockquote><h3>CI votes not forwarded on commit message change</h3> <pre> Key: OVIRT-1895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, If a change goes through this flow:</p> <ol><li><p>Push an update N</p></li> <li><p>CI triggers check-patch for N</p></li> <li><p>Push another update N+1 that changes only commit message</p></li> <li><p>CI marks +1 N</p></li></ol> <p>Then we have logic to not trigger CI for N+1 (with the assumption that a change to commit message should not affect the result), but also do not mark +1 N+1, leaving the patch unmarked. We should either forward the +1, when giving it, to all consecutive future patchsets that only changed the commit message, or give up on the optimization and always trigger CI. As an example, see: <a href="https://gerrit.ovirt.org/87515">https://gerrit.ovirt.org/87515</a> Best regards, — Didi</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518592365-27516-116--

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1895: -------------------------------- Epic Link: OVIRT-400 > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1895) CI votes not forwarded on commit message change
by Barak Korren (oVirt JIRA) 14 Feb '18

14 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1895?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1895: ------------------------------------- [~didi(a)redhat.com] this had been reported many times in the past including by you in OVIRT-1627. See OVIRT-1639 for a tracker for solving this. Closing this ticket as a duplicate > CI votes not forwarded on commit message change > ----------------------------------------------- > > Key: OVIRT-1895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1895 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > If a change goes through this flow: > 1. Push an update N > 2. CI triggers check-patch for N > 3. Push another update N+1 that changes only commit message > 4. CI marks +1 N > Then we have logic to not trigger CI for N+1 (with the assumption that > a change to commit message should not affect the result), but also do > not mark +1 N+1, leaving the patch unmarked. > We should either forward the +1, when giving it, to all consecutive > future patchsets that only changed the commit message, or give up on > the optimization and always trigger CI. > As an example, see: > https://gerrit.ovirt.org/87515 > Best regards, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0