- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4023 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Dec '16

08 Dec '16

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

1 1

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-713: ------------------------------------------------- [~ngoldin(a)redhat.com] anything you're doing now on reposync will solve this? > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-792) Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...'
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-792?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-792: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) please check if still relevant > Jenkins job on fc23-vm05.phx.ovirt.org stuck on '... Removing the used loop devices...' > --------------------------------------------------------------------------------------- > > Key: OVIRT-792 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-792 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nadav Goldin > Assignee: Shlomo Ben David > > Not sure if this is a regression, maybe added in [1], or a temporary glitch: > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/336/console > http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/337/console > for now going to clean it manually. > [1] https://gerrit.ovirt.org/#/c/64511/ -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-886: ------------------------------------------------- Who was the original requestor for this who can verify? > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-911) Move repo closure to run in STD-CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-911?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-911: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Move repo closure to run in STD-CI > ---------------------------------- > > Key: OVIRT-911 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-911 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Daniel Belenky > > Repo closure jobs are currently running on VMs. > We would like to change these jobs to run inside mocks as STD-CI. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-889: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > 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: Daniel Belenky > 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)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-890: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support to publish containers in standard CI > ------------------------------------------------ > > Key: OVIRT-890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Labels: containers, docker, standard-ci > > Mostly likely to Dockerhub or OpenShift registry. > We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] 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)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by Greg Sheremeta (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] 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/epel-…: > [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/epel-… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-854) repoman: check if repoman can keep more than 1 version for experimental repo
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-854?page=com.atlassian.jira.p… ] 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)

1 0