Bug 981576 - Miss validations for SSH Location when configuring kdump with ssh
Miss validations for SSH Location when configuring kdump with ssh
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Fabian Deutsch
Virtualization Bugs
Depends On:
  Show dependency treegraph
Reported: 2013-07-05 03:38 EDT by haiyang,dong
Modified: 2014-01-21 14:44 EST (History)
13 users (show)

See Also:
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:
Last Closed: 2014-01-21 14:44:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 16796 None None None Never

  None (edit)
Description haiyang,dong 2013-07-05 03:38:55 EDT
Description of problem:
Enter Kdump page and input invalid ssh Location "%%%%%%%%%%" to configure kdump with ssh.
Miss validations to prompt users that "%%%%%%%%%%" was invalid input info.

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

How reproducible:

Steps to Reproduce:

Actual result:

Expect result:

Additional info:
Comment 5 haiyang,dong 2013-10-22 04:58:00 EDT
Test version:

Now enter Kdump page and input invalid ssh Location "%%%%%%%%%%" or "root@example.com%" 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".
Comment 7 Cheryn Tan 2013-11-07 19:31:06 EST
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:


Thanks in advance.
Comment 9 errata-xmlrpc 2014-01-21 14:44:39 EST
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.


Note You need to log in before you can comment on or make changes to this bug.