December 2016 - Infra - Ovirt List Archives

[JIRA] (OVIRT-889) Add support for building containers in standard CI

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-889: -------------------------------------------- Priority: Highest (was: Medium) > Add support for building containers in standard CI > -------------------------------------------------- > > Key: OVIRT-889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > Labels: containers, docker > > might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org

by Greg Sheremeta (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira... ] Greg Sheremeta commented on OVIRT-904: -------------------------------------- [~bkorren(a)redhat.com] > are you doing that manually Yes, completely manual > I'm not sure oVirt's own infra would be the best place, because Patternfly is not strictly an oVirt project. True. However, we've talked about renaming the rpm to 'ovirt-patternflyX' to reflect the fact that it's only used by us. In that case, it might make sense to move it to our infra. > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epe...: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epe... -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-854) repoman: check if repoman can keep more than 1 version for experimental repo

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-854?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-854: -------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) We already have a ticket on this, on the rel eng epic > repoman: check if repoman can keep more than 1 version for experimental repo > ---------------------------------------------------------------------------- > > Key: OVIRT-854 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-854 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Today we see text experimental master jobs fails because it has different vdsm rpms versions in the same repo. > This can happen because VDSM has 2 jobs publishing the "same" noarch rpms, once from x86_64 and once from ppc64le. > Since the job only takes latest rpms, it might take a newer rpm from one arch and older rpms from another, causing add host to fail installing VDSM. > We need to check if its possible to tell repoman to keep more than 1 version (should be enough) so the tests won't wait in this period of time where one arch got a head of another one. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-753: -------------------------------------------- Status: Blocked (was: In Progress) > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x... > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-923) define process to manage and apply ansible playbooks

by Evgheni Dereveanchin (oVirt JIRA)

Evgheni Dereveanchin created OVIRT-923: ------------------------------------------ Summary: define process to manage and apply ansible playbooks Key: OVIRT-923 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-923 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low We already have a repository with ansible code, but to use it effectively we need to define a way to manage playbooks and run them effectively. As Ansible Tower is not open source we need to investigate other solutions on the market. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-913) Speed up mock with the `nosync` package

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-913?page=com.atlassian.jira... ] Barak Korren reassigned OVIRT-913: ---------------------------------- Assignee: Barak Korren (was: infra) > Speed up mock with the `nosync` package > --------------------------------------- > > Key: OVIRT-913 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-913 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Labels: mock, mock_runner.sh, standard-ci > > The {{nosync}} package can make mock faster by making it ignore all {{sync(2)}} calls. > {{mock_runner.sh}} actually already enables this setting in the chroot configuration files, but it cannot work without the package. > We need to check if this actually makes mock faster, and if so, add it to the slaves. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-226: -------------------------------------------- Priority: Lowest (was: Medium) > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-449) Add junit report to ovirt-engine standard ci

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-449?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-449: -------------------------------------------- Priority: Low (was: Medium) > Add junit report to ovirt-engine standard ci > -------------------------------------------- > > Key: OVIRT-449 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-449 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > Priority: Low > > Currently there are to ways of doing it: > * Using a special job template for ovirt-engine (easy to do now, hard to maintain/reuse) > * Using jenkins pipeline plugin to dynamically add it to any job that generates a report (hard to do right now, easy to maintain/reuse) -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- [~ybronhei(a)redhat.com] can you check if it works for you now? > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > 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.620.0#100023)

7 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-705) Upgrade to puppet 4.0

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-705?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-705: -------------------------------------------- Priority: Lowest (was: Medium) > Upgrade to puppet 4.0 > --------------------- > > Key: OVIRT-705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-705 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Lowest > > Related to the migration of foreman + puppet master to PHX, and worth its own ticket. > Will be addressed once we have a new foreman 1.12 up & running. > Also, nice blog on the migration might be useful: > http://hggh.github.io/puppet/debian/2016/08/19/puppet-4.x.html -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra December 2016