Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 577703[details]
MessUpScreenPictures
Description of problem:
The screen mess up after some irregular actions.
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120411.0.el6
How reproducible:
100%
Steps to Reproduce:
1. Install rhevh on local host;
2. Configure network;
3. Scroll down to Kernel Dump Menu, choose any one of the NFS/SSH configurations;
4. Input the valid NFS Location/SSH Location, or input nothing;
5. Press the arrows on keyboard, the "Configuration Check" window with gray "OK" was shown,Press the gray "OK".
Actual results:
1. A blank window with <Apply> button comes out[BlankWindowWithApplyButton.png].
2. When press the arrows on keyboard, some part of the Kernel Dump windown was shown.[SomePartOfTheKernelDumpWindow.png]
3. When chose the Restore(Local) option, the window is like this.[ChoseTheRestore(Local)Option.png]
Expected results:
After the 5th step above, the original Kernal Dump windown should be shown correctly. [OriginalWindow.png]
Additional info:
verified with rhevh-6.3-20120426.2, try input invalid kdump nfs/ssh locations, and continue to apply, it po up a kdump status window and show a warn "kdump configuration failed, location unreachable".
the screen is not messed up.
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-2012-0741.html
Created attachment 577703 [details] MessUpScreenPictures Description of problem: The screen mess up after some irregular actions. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.3-20120411.0.el6 How reproducible: 100% Steps to Reproduce: 1. Install rhevh on local host; 2. Configure network; 3. Scroll down to Kernel Dump Menu, choose any one of the NFS/SSH configurations; 4. Input the valid NFS Location/SSH Location, or input nothing; 5. Press the arrows on keyboard, the "Configuration Check" window with gray "OK" was shown,Press the gray "OK". Actual results: 1. A blank window with <Apply> button comes out[BlankWindowWithApplyButton.png]. 2. When press the arrows on keyboard, some part of the Kernel Dump windown was shown.[SomePartOfTheKernelDumpWindow.png] 3. When chose the Restore(Local) option, the window is like this.[ChoseTheRestore(Local)Option.png] Expected results: After the 5th step above, the original Kernal Dump windown should be shown correctly. [OriginalWindow.png] Additional info: