- Infra - oVirt List Archives

[JIRA] (OVIRT-1847) add mzamazal and phoracek to vdsm_stable_maintainers
by danken (oVirt JIRA) 14 Jan '18

14 Jan '18

danken created OVIRT-1847: ----------------------------- Summary: add mzamazal and phoracek to vdsm_stable_maintainers Key: OVIRT-1847 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1847 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: danken Assignee: infra As approved on the mailing list http://lists.ovirt.org/pipermail/devel/2018-January/032400.html please add [~mzamazal(a)redhat.com] and [~phoracek(a)redhat.com] as vdsm stable branch maintainers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 84883,11 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 84883,11 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" 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/84883/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4810/

1 0

[CQ]: 86289,1 (cockpit-ovirt) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jan '18

14 Jan '18

Change 86289,1 (cockpit-ovirt) 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/86289/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/234/

1 0

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

14 Jan '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1101/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 e1c292b6e3a20dcb51c31e307273b589db739ca2 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e1c292b6e3a20dcb51c31e307273b589db739ca2 Commit message: "vdsm: Disable Fedora 26 builds on master" > git rev-list e1c292b6e3a20dcb51c31e307273b589db739ca2 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins366348300979211253.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

[CQ]: 86287, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86287,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86285,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86285,1 (cockpit-ovirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86287/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86285/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/232/

1 0

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image
by eyal edri (oVirt JIRA) 14 Jan '18

14 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1846?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-1846: -------------------------------- Assignee: Gal Ben Haim (was: infra) > New gerrit project - ovirt-node-ng-image > ---------------------------------------- > > Key: OVIRT-1846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yuval Turgeman > Assignee: Gal Ben Haim > > Hi, > We would like to split the squashfs+installer creation from the current > ovirt-node-ng project, leaving it to build its current rpms only (nodectl, > docs, tools etc) according to [1]. > For this we would like to have a new gerrit project `ovirt-node-ng-image`. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120 > Thanks, > Yuval. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image
by Barak Korren (oVirt JIRA) 14 Jan '18

14 Jan '18

This is a multi-part message in MIME format... ------------=_1515944717-26563-108 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1846?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1846: ------------------------------------- [~yuvalt(a)redhat.com] see my comment on the bug, I'm not convinced creating a new repo is the best way to achieve what you want in this point in time. > New gerrit project - ovirt-node-ng-image > ---------------------------------------- > > Key: OVIRT-1846 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yuval Turgeman > Assignee: infra > > Hi, > We would like to split the squashfs+installer creation from the current > ovirt-node-ng project, leaving it to build its current rpms only (nodectl, > docs, tools etc) according to [1]. > For this we would like to have a new gerrit project `ovirt-node-ng-image`. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120 > Thanks, > Yuval. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515944717-26563-108 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1846?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1846:</h3> <p>[~yuvalt(a)redhat.com] see my comment on the bug, I'm not convinced creating a new repo is the best way to achieve what you want in this point in time.</p> <blockquote><h3>New gerrit project – ovirt-node-ng-image</h3> <pre> Key: OVIRT-1846 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yuval Turgeman Assignee: infra</pre> <p>Hi, We would like to split the squashfs+installer creation from the current ovirt-node-ng project, leaving it to build its current rpms only (nodectl, docs, tools etc) according to [1]. For this we would like to have a new gerrit project `ovirt-node-ng-image`. [1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1527120">https://bugzilla.redhat.com/show_bug.cgi?id=1527120</a> Thanks, Yuval.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</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> ------------=_1515944717-26563-108--

1 0

[JIRA] (OVIRT-1680) Adapt STDCI pipelines for use in Gerrit projects
by Daniel Belenky (oVirt JIRA) 14 Jan '18

14 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1680?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1680: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Adapt STDCI pipelines for use in Gerrit projects > ------------------------------------------------ > > Key: OVIRT-1680 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1680 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Daniel Belenky > Labels: gerrit, standard-ci > > So far work on OVIRT-1522 focused on GitHub, and it is now feature-complete. > Now its time to make this work also available for Gerrit projects. > OVIRT-1629 is a blocker for this ticket because the '{{automation.yaml}}' implementation in the current STDCI pipelines does not yet support everything that the existing JJB YAML does. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1846) New gerrit project - ovirt-node-ng-image
by Yuval Turgeman (oVirt JIRA) 14 Jan '18

14 Jan '18

Yuval Turgeman created OVIRT-1846: ------------------------------------- Summary: New gerrit project - ovirt-node-ng-image Key: OVIRT-1846 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1846 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yuval Turgeman Assignee: infra Hi, We would like to split the squashfs+installer creation from the current ovirt-node-ng project, leaving it to build its current rpms only (nodectl, docs, tools etc) according to [1]. For this we would like to have a new gerrit project `ovirt-node-ng-image`. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1527120 Thanks, Yuval. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 86286, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '18

14 Jan '18

A system test invoked by the "ovirt-4.2" change queue including change 86286,1 (cockpit-ovirt) failed. However, this change seems not to be the root cause for this failure. Change 86285,1 (cockpit-ovirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86285,1 (cockpit-ovirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86286/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86285/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/229/

1 0