Bug 980783
Summary: | Better to disable the function "Kernel Dump" using "NFS/SSH" before configured network | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | haiyang,dong <hadong> |
Component: | ovirt-node | Assignee: | Ryan Barry <rbarry> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | acathrow, bsarathy, cboyle, cshao, fdeutsch, gouyang, hadong, huiwa, jboggs, leiwang, mburns, mgoldboi, ovirt-bugs, ovirt-maint, rbarry, ycui |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-node-3.0.1-2.el6 | Doc Type: | Bug Fix |
Doc Text: |
The system was allowing ssh/NFS to be used as a KDump target without a configured network
This meant that the KDump configuration failed because no network was available when the user tried to configure a SSH or NFS location.
This has been fixed by only allowing the KDump ssh/nfs targets to be configured when the network has been configured beforehand.
This means that the user does not run into a situation where the kdump configuration fails because of an unconfigured network
|
Story Points: | --- |
Clone Of: | 966343 | Environment: | |
Last Closed: | 2014-01-21 19:43:21 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: | |||
Bug Depends On: | 947406, 966343, 966498, 1040742 | ||
Bug Blocks: |
Description
haiyang,dong
2013-07-03 08:41:39 UTC
Also can reproduce it in rhev-hypervisor6-6.5-20130222.0.auto1707.el6.iso, so need clone it from upstream bug Component to downstream Component in order to also track it in rhev-h Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 When disabled network, it will prompt "Networking is not configured, please configure it before NFS or SSH-based kdump",also it will disable the function "Kernel Dump" using "NFS/SSH" and didn't display these two types in kdump page. so this bug has been fixed, change the status into "VERIFIED" This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance. Hiya can I ask why it is better to do this? does using some of the options cause issues? Trying to explain for errata text. Thanks (In reply to Charlie from comment #11) > Hiya can I ask why it is better to do this? does using some of the options > cause issues? Trying to explain for errata text. Thanks Need to set network up to configure kdump success via nfs/ssh, so now we redesign kdump page, if users didn't set network up, hide nfs/ssh items, only allow users configure kdump via local. To reiterate, we don't even want to present the option to set kdump options which are invalid because there's no valid network configuration, so they're hidden if networking is not configured. While I agree that changing the notice about networking not being configured to a global notice field would be better, I'm not sure that it's a blocker for this bug, since the current notice implementation works well for this issue. (In reply to Ryan Barry from comment #14) > While I agree that changing the notice about networking not being configured > to a global notice field would be better, I'm not sure that it's a blocker > for this bug, since the current notice implementation works well for this > issue. Yes, we can drop the dependency on the global notice field. Which is more an RFE, Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0033.html |