Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 641157

Summary: Fencing test gives result of AUTO when run, instead of PASS or FAIL
Product: [Retired] Red Hat Hardware Certification Program Reporter: Gary Case <gcase>
Component: Test Suite (harness)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: czhang, gregg.shick, rlandry, yuchen
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In v7 1.2, fencing test gave result of AUTO after run, instead of PASS or FAIL. This issue has been fixed in v7 1.3, now fencing test will give correct PASS/FAIL information when run "v7 print".
 Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-09 16:16:15 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
fencing test patch to mark the test as non-interactive none

Description Gary Case 2010-10-07 21:15:05 UTC 
Description of problem:
The fencing test gives a result of AUTO in the output of v7 print, even after a successful run.

Version-Release number of selected component (if applicable):
v7 1.2-25
RHEL6

How reproducible:
Every time

Steps to Reproduce:
1. Run the fencing test 
2. When complete, run 'v7 print' and look at the results
3.
  
Actual results:
Test Run 1
----------------------------------------------------------------
usb                                                  - 
network eth1    net_00_14_4f_ca_33_f1                - 
network eth0    net_00_14_4f_ca_33_f0                - 
fv_memory                                              - 
fv_storage                                              - 
fv_core                                              - 
fv_network                                              - 
info                                                 - PASS
reboot                                               - 
fencing                                              - AUTO


Expected results:
PASS or FAIL instead of AUTO for the test result.

Additional info:
Comment 1 Rob Landry 2010-11-19 20:10:11 UTC 
Can the results rpm be attached?  I'm not certain if Greg will need it, but just to ask in case it's still available.
Comment 2 Gary Case 2010-11-23 18:46:32 UTC 
I don't have the results file anymore, but I found that it always gave the AUTO result.
Comment 3 Greg Nichols 2011-04-28 16:30:16 UTC 

*** This bug has been marked as a duplicate of bug 679011 ***
Comment 4 Greg Nichols 2011-04-28 18:42:29 UTC 
This still happens on R38 - re-popening.
Comment 5 Greg Nichols 2011-04-28 19:56:51 UTC 
Created attachment 495656 [details]
fencing test patch to mark the test as non-interactive

Even though the initial part of the test is interactive, it gets run via continue --mode auto on subsequent reboots, so it needs to be marked as non-interactive.
Comment 9 Caspar Zhang 2011-05-01 08:49:09 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
In v7 1.2, fencing test gave result of AUTO after run, instead of PASS or FAIL. This issue has been fixed in v7 1.3, now fencing test will give correct PASS/FAIL information when run "v7 print".
Comment 10 Greg Nichols 2011-05-04 22:01:14 UTC 
*** Bug 702131 has been marked as a duplicate of this bug. ***
Comment 11 errata-xmlrpc 2011-05-09 16:16:15 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/RHBA-2011-0497.html