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

Bug 635973

Summary: reboot test should set vmcore size before testing kdump
Product: [Retired] Red Hat Hardware Certification Program Reporter: Caspar Zhang <czhang>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Guangze Bai <gbai>
Severity: medium Docs Contact:
Priority: high    
Version: 1.2CC: qcai, rlandry, sdenham, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In v7 1.2, if a system has large memory, generating and copying vmcore will consume many time, which may cause reboot time beyond expected value. This issue has been fixed in v7 1.3, now a compressed vmcore will be produced in reboot test and this change has been verified on a large memory systems.
Story Points: ---
Clone Of:
: 701491 (view as bug list) Environment:
Last Closed: 2011-05-09 16:13:52 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:
Bug Depends On:    
Bug Blocks: 626970, 701491    
Attachments:
Description Flags
reboot.py patch using makedumpfile to dump vmcore
none
log.py patch to allow appending to existing log files.
none
configfile patch to allow parameter settings to be appended
none
continuation.py patch to set kernel version before reboot, and check it after
none
Caspar's patch to fix several reboot issues
none
Caspar's patch v2 to fix several reboot issues czhang: review?

Description Caspar Zhang 2010-09-21 08:18:45 UTC
Description of problem:

if kdump is enabled during reboot test, copying vmcore may cost several
minutes, so it's easily to take > 10 min to reboot in reboot test.


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

How reproducible:
very often

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 5 Greg Nichols 2011-04-14 14:58:01 UTC
Created attachment 492136 [details]
reboot.py patch using makedumpfile to dump vmcore

This patch makes a number of changes to the reboot test:

1) sets core_collector to makedumpfile -d 31 to produce a compressed core file
If core_collector is previously set, the test will not change it.  If the test adds the setting, it restarts kdump so the new setting is observed.

2) Test output is tagged and preserved both before and after the reboot.

Comment 6 Greg Nichols 2011-04-14 14:59:17 UTC
Created attachment 492137 [details]
log.py patch to allow appending to existing log files.

Comment 7 Greg Nichols 2011-04-14 15:01:34 UTC
Created attachment 492138 [details]
configfile patch to allow parameter settings to be appended

Comment 8 Greg Nichols 2011-04-14 15:18:50 UTC
Created attachment 492140 [details]
continuation.py patch to set kernel version before reboot, and check it after

The patch adds the kernel version to the  "bootstamp" file v7 uses to track state before and after the reboot.   If the kernel versions don't match, the test will fail.

Comment 18 Caspar Zhang 2011-04-30 15:33:04 UTC
Created attachment 495977 [details]
Caspar's patch to fix several reboot issues

Comment 19 Caspar Zhang 2011-05-01 08:14:15 UTC
Created attachment 496030 [details]
Caspar's patch v2 to fix several reboot issues

Comment 20 Caspar Zhang 2011-05-01 08:32:48 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, if a system has large memory, generating and copying vmcore will consume many time, which may cause reboot time beyond expected value. This issue has been fixed in v7 1.3, now a compressed vmcore will be produced in reboot test and this change has been verified on a large memory systems.

Comment 27 errata-xmlrpc 2011-05-09 16:13:52 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