Bug 680910

Summary:	Not deterministic behaviour for /distribution/virt/start.
Product:	[Retired] Beaker	Reporter:	Dimitar Yordanov <dyordano>
Component:	tests	Assignee:	Jeff Burke <jburke>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	high
Version:	0.7	CC:	bpeck, dcallagh, dyordano, jburke, llim, mcsontos, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Misc
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-11 21:35:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dimitar Yordanov 2011-02-28 13:24:59 UTC

Description of problem:
Not deterministic behaviour for /distribution/virt/start. Once it fails once it passes.

Version-Release number of selected component (if applicable):
Version - 0.6.5 

How reproducible:
Time to time.

Steps to Reproduce:
See Jobs:
PASS: https://beaker.engineering.redhat.com/recipes/115958 
FAILS:https://beaker.engineering.redhat.com/recipes/116482
  
Actual results:
Once it fails once it passes.

Expected results:
Always passes.

Additional info:

Comment 1 Bill Peck 2011-03-23 18:48:48 UTC

Gurhan,

Can you look into this for me?

Comment 2 Gurhan Ozen 2011-03-23 20:43:33 UTC

I don't think this is a bug. What /distribution/virt/start does is to issue the start command to the guest. If it encounters error, it errors out. Domain starting and stopping are asynchronous events for libvirt, which means it issues the command to the guest and returns.  In this instance (Recipe 116482), what's happening is that /distribution/virt/start is being called twice in the same job, on the same guest (tasks 1265671 & 1265674 ) and the second start job is being called immediately after a stop job. So the chances are that the guest is still running, though it might be in the process of being shutdown, so the virsh errors out since the guest is still running.

Now, we can definitely either improve this, or have another test to ensure that the stop test waits for the guest to shutdown. In fact, it originally used to do that but logging into the serial console of the guest and waiting for the guest to shutdown but it caused out issues. 

Would you want such capability?

Comment 3 Dimitar Yordanov 2011-03-24 08:04:22 UTC

I supposed that probably the Guest is still shuting down so I tried  rh-tests-distribution-virt-guest-reboot but it was failing too.

Comment 6 Jeff Burke 2013-11-04 13:26:15 UTC

Dimitar Yordanov,
 Is this still an issue? Gurhan had made a nuber of changes in recent months. I am hoping that this one was eresolved. If not we will have to reassign it to someone willing to take over the virt/install task.

Thanks,
Jeff