Previously, SSH could be configured for kdump when an incorrect password was provided. kdump now verifies that the SSH connection is set up successfully before finishing configuration. If a wrong password is provided, an error message appears explaining that kdump configuration failed because the location was unreachable.
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', user will be lead to the login page.
Login fail, though correct password was provided.
Reboot the system and login, on the Kdump page, it shows as SSH configured successfully with the SSH location info.
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121015.1.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:
User was lead to the login page.
Login failed, though correct password was provided.
Rebooted the system and login, on the Kdump page, it shown as SSH has been configured successfully with the SSH location info.
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.3-20121023.0.el6_3, so it is a regression bug.
http://gerrit.ovirt.org/#/c/10064/
Tested as follows:
1. Install with patch applied
2. Configure network with dhcp
3. Configure KDUMP with valid ssh url
4. Hit Apply
5. Password prompt appears: Press ctrl+c twice
6. TUI appears again showing empty fields and /etc/kdump.conf/.old don't exist
Working on this uncovered bug 891558.
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-2013-0556.html