Bug 713121

Summary: v7 1.3 R46 Reboot test fails on RHEL5.6 Xen
Product: [Retired] Red Hat Hardware Certification Program Reporter: Karthick Rajaram <karthicr>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED CURRENTRELEASE QA Contact: Guangze Bai <gbai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.3CC: czhang, gbai, gcase, jwilleford, rlandry, stbechto, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-11 14:41:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 767775, 773757    
Attachments:
Description Flags
V7 test result - rpm
none
sosreport none

Description Karthick Rajaram 2011-06-14 11:09:22 UTC
Created attachment 504647 [details]
V7 test result - rpm

Description of problem:
  Reboot test fails on RHEL5.6 system. The system hangs when it starts rpc idmapd.
Reboot test (both local and nfs fail). System gets stuck at “Starting RPM idmapd: Error : RPC MTAB does not exist”. Tried with v7 1.2-25, system stucks at the same point.

Version-Release number of selected component (if applicable):
v7 1.2 R25,  v7 1.3 R46


How reproducible:
Every time

Steps to Reproduce:
1.Install RHEL5.6
2.Install Xen
3.Install v7. Run reboot test.
  
Actual results:
Test failed

Expected results:
Test should pass

Additional info:

Comment 1 Karthick Rajaram 2011-06-14 11:11:34 UTC
Created attachment 504649 [details]
sosreport

Comment 4 Gary Case 2011-11-02 17:30:18 UTC
Karthick,

here are the commands that the test can use, depending on whether kdump is configured or if it is not:

Kdump enabled
-------------
echo 1 > /proc/sys/kernel/sysrq
echo "c" > /proc/sysrq-trigger
            
Kdump not enabled
-----------------
shutdown -r 0

It could be that your system is not configured to reboot properly after a panic. Can you tell me the contents of /proc/sys/kernel/panic ? I expect it to be a zero. 

-Gary

Comment 9 Jason Willeford 2012-05-11 15:38:36 UTC
Karthick,
Is this still an issue with latest RHEL 5 and latest v7?  I'm likely to close this soon.

Comment 11 Jason Willeford 2012-08-06 17:32:33 UTC
Rob,
I spoke with Karthick today, he said that he will try to test this with the latest v7.

Comment 12 Karthick Rajaram 2012-08-13 16:08:00 UTC
Issue not seen with v7-1.4-38 and RHEL5.8
Reboot test just works fine.