Red Hat Bugzilla – Bug 989391
TUI:need to fix kdump page refresh after save
Last modified: 2014-06-09 10:07:28 EDT
Created attachment 779675 [details] attached Screenshot for kdump page Description of problem: On the Kernel Dump page, select SSH with a valid SSH location. After configure kdump via SSH successfully, configured info: SSH Location (root@example.com): root@10.66.11.23_______ will show in kdump page. Then select "() Disable" to disable kdump profile, after disable it success, but check that configured info: SSH Location (root@example.com): root@10.66.11.23_______ still was shown in kdump page (seen kdump.png) 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. Select "() Disable" to disable kdump profile Actual results: After step 3, configured info: SSH Location (root@example.com): root@10.66.11.23_______ still was shown in kdump page Expected results: After step 3, "() Disable" should be selected and the kdump profile should be deleted from TUI and "/etc/kdump.conf" Additional info:
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Test version: rhevh-6.5-20131220.0 ovirt-node-3.0.1-13.el6_5.noarch Test steps: 1. Install rhevh and set network 2. On the Kernel Dump page, select SSH with a valid SSH location or NFS with valid NFS location. 3. Select "() Disable" to disable kdump profile Test results: After step 3, "() Disable" was selected and the kdump profile was deleted from TUI and "/etc/kdump.conf", 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 Thank you for your help.
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