Bug 1032908
Summary: | makedumpfile fails on s390x | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Qiao Zhao <qzhao> |
Component: | kexec-tools | Assignee: | kdump team <kdump-team-bugs> |
Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | anderson, vgoyal |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | s390x | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-21 16:29:11 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: | |
Embargoed: |
Description
Qiao Zhao
2013-11-21 08:51:18 UTC
Given that makedumpfile is doing what it is supposed to do, which is fail if it receives a bogus command line argument, I have a few questions: - What do you expect that it should do? - Why s390x only? - Is the addition of -nosuchoption a new QA feature that you are implementing as part of testing all commands? (In reply to Qiao Zhao from comment #0) > Description of problem: > makedumpfile fails on s390x with kexec-tools-2.0.13.el7.s390x. > https://beaker.engineering.redhat.com/recipes/1139255 > http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2013/11/5473/547365/ > 1139255/console.log > > Version-Release number of selected component (if applicable): > kernel-3.10.0-50.el7 > kexec-tools-2.0.4-13.el7 > > How reproducible: > always > > Steps to Reproduce: > 1. Install RHEL-7.0-20131115.2 > 2. setup kdump environment > --- > xfs /dev/mapper/rhel_ibm--z10--28-root > path /var/crash > core_collector makedumpfile -nosuchoption Why are you passing -nosuchoption. This is not a valid option and if you pass invalid option to makedumpfile it will fail. Closing this bug as NOTABUG. Hi Dave and Vivek, Is my folly, I know this is a wrong approach from bhe@ at yesterday afternoon, he give me a good answer. Thanks, Qiao |