- Infra - oVirt List Archives

[JIRA] (OVIRT-665) Jenkins: gerrit trigger plugin issues after update
by Evgheni Dereveanchin (oVirt JIRA) 28 Jul '16

28 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-665?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-665: -------------------------------------------- The recommended workaround is to whitelist the parameters in hudson.model.ParametersAction.safeParameters For gerrit trigger they are: GERRIT_EVENT_TYPE,GERRIT_EVENT_HASH,GERRIT_BRANCH,GERRIT_TOPIC, GERRIT_CHANGE_NUMBER,GERRIT_CHANGE_ID,GERRIT_PATCHSET_NUMBER, GERRIT_PATCHSET_REVISION,GERRIT_REFSPEC,GERRIT_PROJECT,GERRIT_CHANGE_SUBJECT, GERRIT_CHANGE_COMMIT_MESSAGE,GERRIT_CHANGE_URL,GERRIT_CHANGE_OWNER, GERRIT_CHANGE_OWNER_NAME,GERRIT_CHANGE_OWNER_EMAIL, GERRIT_PATCHSET_UPLOADER,GERRIT_PATCHSET_UPLOADER_NAME To add them we can set the list in JENKINS_JAVA_OPTIONS of /etc/sysconfig/jenkins > Jenkins: gerrit trigger plugin issues after update > -------------------------------------------------- > > Key: OVIRT-665 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-665 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: infra > > It looks like the Gerrit trigger plugin is broken after yesterday's release due to SECURITY-170 implemented in the new Jenkins version: > https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SEC… > Sample failing triggered build: > http://jenkins.ovirt.org/job/infra-puppet_production_check-puppet-manifests… -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

[JIRA] (OVIRT-665) Jenkins: gerrit trigger plugin issues after update
by Evgheni Dereveanchin (oVirt JIRA) 28 Jul '16

28 Jul '16

Evgheni Dereveanchin created OVIRT-665: ------------------------------------------ Summary: Jenkins: gerrit trigger plugin issues after update Key: OVIRT-665 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-665 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Evgheni Dereveanchin Assignee: infra It looks like the Gerrit trigger plugin is broken after yesterday's release due to SECURITY-170 implemented in the new Jenkins version: https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SEC… Sample failing triggered build: http://jenkins.ovirt.org/job/infra-puppet_production_check-puppet-manifests… -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

Please create an SLA team group in gerrit
by Roy Golan 28 Jul '16

28 Jul '16

dear infra, It will be very helpful to have an SLA team setup for quick add in review. Can you help? (I will supply the members if needed) \R

4 6

[JIRA] (OVIRT-663) add ppc64le arch builds for oVirt projects
by Francesco Romani (oVirt JIRA) 28 Jul '16

28 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-663?page=com.atlassian.jira.p… ] Francesco Romani commented on OVIRT-663: ---------------------------------------- Looking at the vdsm.spec: - mom should be noarch - python-cpopen, but should be there already I guess - python-pthreading should be noarch - ovirt-vmconsole is noarch So everything else should be ok > add ppc64le arch builds for oVirt projects > ------------------------------------------ > > Key: OVIRT-663 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-663 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > now that we have a ppc64le slaves in jenkins we can start building pkg for it and deploy it to resources.ovirt.org. > this ticket will track all pkg progress: > # qemu-kvm - currently pending gluster builds for ppc64le, ETA - next week > # vdsm > # ioprocess > [~danken][~fromani(a)redhat.com] anything else that is not noarch which we need to build? -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

[JIRA] (OVIRT-664) add emails alerts to infra on test ovirt experimental repos
by eyal edri [Administrator] (oVirt JIRA) 28 Jul '16

28 Jul '16

eyal edri [Administrator] created OVIRT-664: ----------------------------------------------- Summary: add emails alerts to infra on test ovirt experimental repos Key: OVIRT-664 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-664 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: Highest The most critical jobs right now doesn't have email alerts. We need to enable it for all versions flows : http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/ http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0 http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6 -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

[JIRA] (OVIRT-663) add ppc64le arch builds for oVirt projects
by eyal edri [Administrator] (oVirt JIRA) 28 Jul '16

28 Jul '16

eyal edri [Administrator] created OVIRT-663: ----------------------------------------------- Summary: add ppc64le arch builds for oVirt projects Key: OVIRT-663 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-663 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra now that we have a ppc64le slaves in jenkins we can start building pkg for it and deploy it to resources.ovirt.org. this ticket will track all pkg progress: # qemu-kvm - currently pending gluster builds for ppc64le, ETA - next week # vdsm # ioprocess [~danken][~fromani(a)redhat.com] anything else that is not noarch which we need to build? -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
by eyal edri [Administrator] (oVirt JIRA) 28 Jul '16

28 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-416: ------------------------------------------------- [~sbonazolla(a)redhat.com] [~mperina] do you know if today check-merged.sh in ovirt-engine is building the same RPMs as build-artifacts? Potentially they can be different since its a different bash script, but if they are the same we can save a lot of time running duplicate rpm builds... Now that we enabled GWT compilation per patch, maybe we can drop the rpm build on check-merged.sh and just do it in build-artifacts? we'll find an error in either jobs anyway.. what do you think? > [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any > ------------------------------------------------------------------------------------- > > Key: OVIRT-416 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > > Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding. > Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?| -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

bad image on ovirt-image-repository "Fedora 24 Cloud Base Image v20160712"
by Yedidyah Bar David 28 Jul '16

28 Jul '16

Hi all, When trying importing this image in the web admin, it fails. engine.log might indicate a problem on the glace server: 2016-07-28 09:44:14,860 ERROR [org.ovirt.engine.core.bll.storage.repoimage.ImportRepoImageCommand] (default task-7) [47a28910] Error during ValidateFailure.: com.woorea.openstack.base.client.OpenStackResponseException: Internal Server Error Please handle. Thanks. Also, it's a bit unclear what are "Fedora 24 Cloud Base Image v20160712 for x86_64 (4490284)" and "Fedora 24 Cloud Base Image v1.2 for x86_64 (2faafb6)". If they have different purposes, please clarify in their names. If one is simply older, it might be better to remove it. Thanks. Best, -- Didi

2 1

[JIRA] (OVIRT-633) Re: [ovirt-devel] [ACTION REQUIRED] broken dependency with vdsm git6e84643
by eyal edri [Administrator] (oVirt JIRA) 28 Jul '16

28 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-633?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-633: -------------------------------------------- Resolution: Fixed Status: Done (was: Blocked) > Re: [ovirt-devel] [ACTION REQUIRED] broken dependency with vdsm git6e84643 > -------------------------------------------------------------------------- > > Key: OVIRT-633 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-633 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > On Wed, Jul 13, 2016 at 10:14 AM, Michal Skrivanek < > michal.skrivanek(a)redhat.com> wrote: > > > > > On 13 Jul 2016, at 09:42, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > > > On Wed, Jul 13, 2016 at 10:04 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> > > wrote: > > >> DEBUG util.py:417: Error: Package: > > >> vdsm-4.18.999-232.git6e84643.el7.centos.x86_64 (ovirt-master-snapshot) > > >> DEBUG util.py:417: Requires: safelease >= 1.0-7 > > >> DEBUG util.py:417: Available: safelease-1.0-5.el7.x86_64 > > >> (centos-epel) > > >> DEBUG util.py:417: safelease = 1.0-5.el7 > > > > > > Yaniv, 1.0-7 not available on centos? > > > > > > https://dl.fedoraproject.org/pub/epel/7/x86_64/s/safelease-1.0-7.el7.x86_64… > > Sandro, wrong repos set up? > > > > > Maybe mirror not aligned or proxy issue. Adding infra. > > > > > >> > > >> > > >> -- > > >> Sandro Bonazzola > > >> Better technology. Faster innovation. Powered by community > > collaboration. > > >> See how it works at redhat.com > > >> > > >> _______________________________________________ > > >> Devel mailing list > > >> Devel(a)ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/devel > > > _______________________________________________ > > > Devel mailing list > > > Devel(a)ovirt.org > > > http://lists.ovirt.org/mailman/listinfo/devel > > > > > > > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project
by eyal edri [Administrator] (oVirt JIRA) 28 Jul '16

28 Jul '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-612: ------------------------------------------------- Hey, Did you got a chance to read on the standard CI ? do you need help in adding the 1st job? > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.184.1#100008)

1 0