- Infra - oVirt List Archives

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Tal Nisan (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Tal Nisan commented on OVIRT-2264: ---------------------------------- [~derez(a)redhat.com] you are the current QE contact, can you please have a look? > 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)

1 0

[JIRA] (OVIRT-2301) cq job stuck for 6 days
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2301: ------------------------------------- The full job log tells you the right story: {code} Resuming build at Wed Jul 04 18:30:12 UTC 2018 after Jenkins restart Waiting to resume part of ovirt-4.2_change-queue-tester #2570: ??? [Pipeline] End of Pipeline java.lang.IllegalStateException: JENKINS-37121: something already locked /home/jenkins/workspace/ovirt-4.2_change-queue-tester at org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:75) at org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:51) at org.jenkinsci.plugins.workflow.support.pickles.TryRepeatedly$1.run(TryRepeatedly.java:92) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) Caused: java.io.IOException: Failed to load build state at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:854) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:852) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:906) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE {code} > 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 > Labels: ost_failures, ost_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-queue-… > 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)

1 0

[JIRA] (OVIRT-2301) cq job stuck for 6 days
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2301: ------------------------------------- Nothing can be stuck for 6 days (we have timeouts defined) - if it is it means jenkins was shut down while it was running (which can cause pipeline jobs for freeze and not resume), and it should be aborted. Although by the looks of it, this might have run while using a buggy modified version of the pipeline code, [~dbelenky(a)redhat.com] can you confirm? > 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 > Labels: ost_failures, ost_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-queue-… > 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)

1 0

[JIRA] (OVIRT-2301) cq job stuck for 6 days
by Dafna Ron (oVirt JIRA) 10 Jul '18

10 Jul '18

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-queue-… 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)

1 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) 10 Jul '18

10 Jul '18

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

1 0

[JIRA] (OVIRT-2300) tested was corrupted
by Ehud Yonasi (oVirt JIRA) 10 Jul '18

10 Jul '18

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

1 0

[JIRA] (OVIRT-2300) tested was corrupted
by Ehud Yonasi (oVirt JIRA) 10 Jul '18

10 Jul '18

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

1 0

[JIRA] (OVIRT-2300) tested was corrupted
by Ehud Yonasi (oVirt JIRA) 10 Jul '18

10 Jul '18

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)

1 0

[JIRA] (OVIRT-2299) permissions to execute manual jenkins jobs
by Dafna Ron (oVirt JIRA) 10 Jul '18

10 Jul '18

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

1 0

[JIRA] (OVIRT-2299) permissions to execute manual jenkins jobs
by Miguel Duarte de Mora Barroso (oVirt JIRA) 10 Jul '18

10 Jul '18

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)

1 0