Bug 514044

Summary: vm.sh does will fail resource if "no state" is detected
Product: Red Hat Enterprise Linux 5 Reporter: Shane Bradley <sbradley>
Component: rgmanagerAssignee: Lon Hohberger <lhh>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 5.5CC: berrange, cfeist, cluster-maint, djansa, edamato, hbrock, jplans, lsmid, tao
Target Milestone: rcKeywords: OtherQA, Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rgmanager-2.0.52-1.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 11:04:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch that adds "no state" to valid running states none

Description Shane Bradley 2009-07-27 18:35:58 UTC 
Description of problem:

When vm.sh does a status check, sometimes "no state" is returned. That
state is currently not a "running" state. Thus the status check fails.

The "no state" should be treated as a running state. 

Version-Release number of selected component (if applicable):
rgmanager-2.0.51-1.el5-x86_64 (5.4 beta)

How reproducible:
Very hard and random.

Steps to Reproduce:
1. Somehow get libvirt to return "no state" on status check
2. vm.sh detects "no state"
3. Then resource is labeled as failed.
  
Actual results:
The vm.sh will return a failed status check.

Expected results:
The vm.sh should return a success on status check.

Additional info:
Patch is attached to the case.
Comment 1 Shane Bradley 2009-07-27 18:36:35 UTC 
Created attachment 355304 [details]
Patch that adds "no state" to valid running states
Comment 5 Lon Hohberger 2009-07-29 14:34:26 UTC 
http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=08f5d180d1a6e3b376a2f0864368840ff264700b
Comment 9 errata-xmlrpc 2009-09-02 11:04:12 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2009-1339.html