deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph J. VLcek (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-493) RHEVm - instance.stop fails and instance returns to RUNNING state.
Date Thu, 28 Feb 2013 20:23:12 GMT


Joseph J. VLcek commented on DTACLOUD-493:

This is not a Deltacloud issue. It is a RHEVm bug:"

Also the rhevm drive test is currently skipped because of this RHEVm BZ, see:

I'll leaving this open and assigned to me to confirm it is resolved and the skip is removed
from the test 
once the RHEVm BZ is fixed.
> RHEVm -  instance.stop fails and instance returns to RUNNING state. 
> --------------------------------------------------------------------
>                 Key: DTACLOUD-493
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Bug
>            Reporter: Joseph J. VLcek
>            Assignee: Joseph J. VLcek
> While attempting to rerecord the VCR episodes/fixture for the test:
> |tests/drivers/rhevm/instance_test.rb  one test fails waiting for the
> instance to stop.
> The test is: "must allow to create a new instance and make it running"
> After the test issues:
>  @driver.stop_instance(
> the test then proceeds to wait_for! the instance to become stopped
>   instance = instance.wait_for!(@driver, record_retries('stop')) { |i| i.is_stopped?
> See:
> The issue is the instance fails to stop and it actually returns to a running state, which
I have observerd
> by extending the timeout on record_retires to a stupid long time
> e.g.:
> instance = instance.wait_for!(@driver, record_retries('stop', :timeout => 99999999))
{  |i| i.is_stopped? }
> and by monitoring the instances "events" using the RHEVm dashboard, where the following
> is displayed:
> "Shutdown of VM i-1361484708 failed."
> and the instance returns to the RUNNING state.
> This is blocking the rerecording of the VCR episodes/fixture or the rhevm instance tests.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message