July 2018 - Infra - Ovirt List Archives

[CQ]: 92843,10 (ovirt-provider-ovn) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 92843,10 (ovirt-provider-ovn) 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/92843/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2601/

6 years, 4 months

1
0
0 / 0

OST manual jobs are pending indefinitely[0]

by Leon Goldberg

A lot of the below: (pending—Jenkins doesn’t have label integ-tests; lfedora1.lf-dev.marist.edu doesn’t have label integ-tests; mirrors.phx.ovirt.org doesn’t have label integ-tests; ovirt-srv17.phx.ovirt.org <https://jenkins.ovirt.org/computer/ovirt-srv17.phx.ovirt.org> is offline; ovirt-srv21.phx.ovirt.org <https://jenkins.ovirt.org/computer/ovirt-srv21.phx.ovirt.org> is offline; ovirt-srv26.phx.ovirt.org <https://jenkins.ovirt.org/computer/ovirt-srv26.phx.ovirt.org> is offline; templates02.phx.ovirt.org doesn’t have label integ-tests; vm0001.workers-phx.ovirt.org doesn’t have label integ-tests; vm0003.workers-phx.ovirt.org doesn’t have label integ-tests; vm0004.workers-phx.ovirt.org doesn’t have label integ-tests; vm0005.workers-phx.ovirt.org doesn’t have label integ-tests; vm0006.workers-phx.ovirt.org doesn’t have label integ-tests; vm0007.workers-phx.ovirt.org doesn’t have label integ-tests; vm0008.workers-phx.ovirt.org doesn’t have label integ-tests; vm0009.workers-phx.ovirt.org doesn’t have label integ-tests; vm0010.workers-phx.ovirt.org doesn’t have label integ-tests; vm0011.workers-phx.ovirt.org doesn’t have label integ-tests; vm0012.workers-phx.ovirt.org doesn’t have label integ-tests; vm0013.workers-phx.ovirt.org doesn’t have label integ-tests; vm0014.workers-phx.ovirt.org doesn’t have label integ-tests; vm0015.workers-phx.ovirt.org doesn’t have label integ-tests; vm0016.workers-phx.ovirt.org doesn’t have label integ-tests; vm0034.workers-phx.ovirt.org doesn’t have label integ-tests; vm0035.workers-phx.ovirt.org doesn’t have label integ-tests; vm0036.workers-phx.ovirt.org doesn’t have label integ-tests; [0] https://jenkins.ovirt.org/job/ovirt-system-tests_manual/

6 years, 4 months

3
3
0 / 0

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jir... ] Evgheni Dereveanchin commented on OVIRT-2287: --------------------------------------------- "HOST did not satisfy internal filter Memory" is an oVirt error. It means that the hypervisor VMs was created with not enough memory (or it had memory but used it for something else) - this shouldn't be related to the amount of free memory on the bare metal. As Barak pointed out, LagoInitFile needs to be verified to ensure enough resources are allocated to hypervisor VMs. > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/... > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

Change in stdci-staging[master]: Dummy change to test nod allocation

by review＠gerrit-staging.phx.ovirt.org

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/169 to look at the new patch set (#3). Change subject: Dummy change to test nod allocation ...................................................................... Dummy change to test nod allocation DO NOT MERGE Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M automation/check-patch.sh M build.sh M change 3 files changed, 5 insertions(+), 5 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stdci-staging refs/changes/69/169/3 -- To view, visit https://gerrit-staging.phx.ovirt.org/169 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Gerrit-Change-Number: 169 Gerrit-PatchSet: 3 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

6 years, 4 months

1
0
0 / 0

Change in stdci-staging[master]: Dummy change to test nod allocation

by review＠gerrit-staging.phx.ovirt.org

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/169 to look at the new patch set (#2). Change subject: Dummy change to test nod allocation ...................................................................... Dummy change to test nod allocation DO NOT MERGE Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M automation/check-patch.sh M change 2 files changed, 3 insertions(+), 3 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stdci-staging refs/changes/69/169/2 -- To view, visit https://gerrit-staging.phx.ovirt.org/169 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Gerrit-Change-Number: 169 Gerrit-PatchSet: 2 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

6 years, 4 months

1
0
0 / 0

Change in stdci-staging[master]: Dummy change to test nod allocation

by review＠gerrit-staging.phx.ovirt.org

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/169 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Gerrit-Change-Number: 169 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 09 Jul 2018 11:49:49 +0000 Gerrit-HasComments: No

6 years, 4 months

1
0
0 / 0

[CQ]: da6ca09 (ovirt-ansible-infra) failed "ovirt-master" system tests

by oVirt Jenkins

Change da6ca09 (ovirt-ansible-infra) 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://github.com/oVirt/ovirt-ansible-infra/commit/da6ca09a2e269f742cc43... For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8624/

6 years, 4 months

1
0
0 / 0

Change in stdci-staging[master]: Dummy change to test nod allocation

by review＠gerrit-staging.phx.ovirt.org

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/169 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Gerrit-Change-Number: 169 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 09 Jul 2018 11:06:00 +0000 Gerrit-HasComments: No

6 years, 4 months

1
0
0 / 0

Change in stdci-staging[master]: Dummy change to test nod allocation

by review＠gerrit-staging.phx.ovirt.org

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/169 ) Change subject: Dummy change to test nod allocation ...................................................................... Patch Set 1: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/169 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ibf51dc6db9a33094ad0bae6d2f0089d547cd5b8c Gerrit-Change-Number: 169 Gerrit-PatchSet: 1 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 09 Jul 2018 10:46:10 +0000 Gerrit-HasComments: No

6 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2264: ---------------------------------- This is reported already to the storage team. I actually found that the problematic task is copy of template which is taking longer then expected. We had a discussion about fixing the tests so that tests will be able to re-try and fail with timeout in case of running tasks since this is not something we can solve in code and is failing randomly a lot. > Cannot deactivate Storage while there are running tasks on this Storage > ----------------------------------------------------------------------- > > Key: OVIRT-2264 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2264 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we failed test: 007_sd_reattach.deactivate_storage_domain in vdsm project with error: Cannot deactivate Storage while there are running tasks on this Storage. -Please wait until tasks will finish and try again.]". HTTP response code is 409. > I am opening this as a race in case something changed in OST tests which would cause this to repeat. > https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506 > https://gerrit.ovirt.org/#/c/92313/2 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2018