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.
Description of problem:
The kdump addon TUI checks user suggested reserved memory size but does not display it anywhere. This complicates inputting a valid value quite a bit, especially as the range changes due to RAM size and other factors.
Version-Release number of selected component (if applicable):
Kdump in RHEL 7.2
How reproducible:
always
Steps to Reproduce:
1. start installation in text mode
2. enter the kdump spoke
3. try to set the amount of reserved memory
Actual results:
The option simply says "Reserve amount(MB)" without any indication which values are accepted. The basically has to guess which value fits to the expected range as incorrect input only returns the unhelpful "You have provided an invalid value" error message.
Expected results:
The option shows the range of valid reserved memory values, for example:
"Reserve amount (128-1792 MB)"
This makes it easy for the user to set the correct value.
Additional info:
I have opened a pull request that makes the kdump addon TUI display the valid reserved memory range:
https://github.com/daveyoung/kdump-anaconda-addon/pull/10
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.
https://rhn.redhat.com/errata/RHEA-2016-2466.html