July 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2301) cq job stuck for 6 days

by Dafna Ron (oVirt JIRA)

Dafna Ron created OVIRT-2301: -------------------------------- Summary: cq job stuck for 6 days Key: OVIRT-2301 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2301 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra [~ederevea] noticed that this job has been stuck for 6 days: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2570/ The job got stuck while waiting for build-artifacts: http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queu... before he restarts jenkins I though [~bkorren(a)redhat.com] or [~dbelenky(a)redhat.com] would like to take a look. the job is still reported as active -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

5 years, 12 months

1
0
0 / 0

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

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2287: ---------------------------------- I will look at the Lagoinit file and submit a patch. > 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)

5 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-2300) tested was corrupted

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2300?page=com.atlassian.jir... ] Ehud Yonasi reassigned OVIRT-2300: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > tested was corrupted > -------------------- > > Key: OVIRT-2300 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2300 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > Labels: cq-issue-traking, ost_failures, tested > > tested partition got corrupted due to a mistake i've made in the cleanup retention policy ticket. > the issue has been fixed and tested was restored from snapshots. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

5 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-2300) tested was corrupted

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2300?page=com.atlassian.jir... ] Ehud Yonasi updated OVIRT-2300: ------------------------------- Resolution: Fixed Status: Done (was: To Do) > tested was corrupted > -------------------- > > Key: OVIRT-2300 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2300 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures, tested > > tested partition got corrupted due to a mistake i've made in the cleanup retention policy ticket. > the issue has been fixed and tested was restored from snapshots. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

5 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-2300) tested was corrupted

by Ehud Yonasi (oVirt JIRA)

Ehud Yonasi created OVIRT-2300: ---------------------------------- Summary: tested was corrupted Key: OVIRT-2300 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2300 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Ehud Yonasi Assignee: infra tested partition got corrupted due to a mistake i've made in the cleanup retention policy ticket. the issue has been fixed and tested was restored from snapshots. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

5 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-2299) permissions to execute manual jenkins jobs

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2299?page=com.atlassian.jir... ] Dafna Ron reassigned OVIRT-2299: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > permissions to execute manual jenkins jobs > ------------------------------------------ > > Key: OVIRT-2299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2299 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Miguel Duarte de Mora Barroso > Assignee: Evgheni Dereveanchin > > Hello, > I would like to run ovirt system tests on jenkins targeting other > builds - e.g. ovirt-provider-ovn / engine rpms generated in other > builds. > From what I've understood, I need to run the test suite, configuring > it with the target build url in the build parameters (accessed through > 'build with parameters' tab. > I can't find that, which leads me to believe I don't have permissions > to execute the builds myself. Could I be grantted enough permissions > to execute this use case? > If I'm wrong and this stems from other causes, let me know. > My jenkins user ID is mbarroso. > Thanks in advance, > Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

5 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-2299) permissions to execute manual jenkins jobs

by Miguel Duarte de Mora Barroso (oVirt JIRA)

Miguel Duarte de Mora Barroso created OVIRT-2299: ---------------------------------------------------- Summary: permissions to execute manual jenkins jobs Key: OVIRT-2299 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2299 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Miguel Duarte de Mora Barroso Assignee: infra Hello, I would like to run ovirt system tests on jenkins targeting other builds - e.g. ovirt-provider-ovn / engine rpms generated in other builds. From what I've understood, I need to run the test suite, configuring it with the target build url in the build parameters (accessed through 'build with parameters' tab. I can't find that, which leads me to believe I don't have permissions to execute the builds myself. Could I be grantted enough permissions to execute this use case? If I'm wrong and this stems from other causes, let me know. My jenkins user ID is mbarroso. Thanks in advance, Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

5 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

by Yuval Turgeman (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ] Yuval Turgeman commented on OVIRT-2201: --------------------------------------- For ovirt-node-ng, we generate a latest-installation-iso.html in build-artifacts, and the download page[1] points to the last successful build per ovirt version. It looks like we can't do it in V2 today. [1] https://www.ovirt.org/node/ > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu... > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE 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)

5 years, 12 months

1
0
0 / 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 557 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/557/ Build Number: 557 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #557 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- No tests ran.

5 years, 12 months

1
1
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 3: 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: 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> Gerrit-Comment-Date: Tue, 10 Jul 2018 05:33:25 +0000 Gerrit-HasComments: No

5 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2018