Bug 981576
Summary: | Miss validations for SSH Location when configuring kdump with ssh | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | haiyang,dong <hadong> |
Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> |
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, ovirt-maint, ycui |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-node-3.0.0-6.el6 | Doc Type: | Bug Fix |
Doc Text: |
When a ssh location was entered on the kdump page, there was no validation to check on the authenticity of the location. Validation for the authenticity of the ssh location
when configuring kdump with ssh has been added, and if the location is invalid, the following message is displayed: "The field must contain an empty string or a valid SSH Address".
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2014-01-21 19:44:39 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
haiyang,dong
2013-07-05 07:38:55 UTC
Fixed in http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=commit;h=2ba8aadccff14c159580f782de19a556b81a9363 Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 Now enter Kdump page and input invalid ssh Location "%%%%%%%%%%" or "root%" to configure kdump with ssh. it will prompt users that "The field must contain an empty string or a valid SSH Address". 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. 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 |