Bug 1043724

Summary: FV tests wait an hour for a time-out when the guest doesn't even start
Product: Red Hat Certification Program Reporter: Greg Nichols <gnichols>
Component: redhat-certification-hardwareAssignee: brose
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0CC: brose, gnichols, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-23 03:45:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Greg Nichols 2013-12-17 02:01:18 UTC 
Description of problem:

In situations where the guest does not start properly, the fv_* tests often must wait for the 60 min. timeout before failing, and often with little or no error messages to help diagnose the problem.

It would be better if there was some sort of handshake between the host and the guest to indicate whether or not the guest started successfully, and failing immediately if this initial check fails, and perhaps gather any error logging provided by libvirtd/qemu in the process.

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

hwcert 1.6.5/1.7.0