Red Hat Bugzilla – Bug 989389
Catch the "KeyboardInterrupt" when inputting "Ctrl+c" during configuring KDump SSH
Last modified: 2014-01-21 14:47:16 EST
Description of problem: On the Kernel Dump page, select SSH with a valid SSH location. Giving a wrong password/Not providing password under the command line and enter 'Ctrl+c' and 'exit', rhev-h will throw an "KeyboardInterrupt" exception and quit the whole application. user will be lead to the login page. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.5-20130725.0.el6 How reproducible: Always Steps to Reproduce: 1. Install rhevh and set network 2. On the Kernel Dump page, select SSH with a valid SSH location. 3. Giving a wrong password/Not providing password under the command line and enter 'Ctrl+c' and 'exit' Actual results: rhev-h will throw an "KeyboardInterrupt" exception and quit the whole application. user will be lead to the login page. Expected results: Provide a better way to lead user back to the configuration page SSH should not be set successfully until correct password is provided Additional info: No such issue in rhevh-6.4.z, so it is a regression bug.
Test version: rhevh-6.5-20131024.1.0.iso ovirt-node-3.0.1-6.el6.noarch Test Steps: 1. Install rhevh and set network 2. On the Kernel Dump page, select SSH with a valid SSH location. 3. Giving a wrong password/Not providing password under the command line and enter 'Ctrl+c' Now it try to catch KeyboardInterrupt and remove kdump configured files instead of quitting the whole application so this bug has been fixed, change it 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