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.
A fault in a regular expression causes Kdump to report invalid NFS server addresses for valid NFS servers. A patch for ovirt-node fixes the regular expression and a user can now enter valid NFS servers addresses for Kdump without error.
Created attachment 483111[details]
"Invalid NFS Entry"
Description of problem:
"Invalid NFS Entry" message display while configure a valid nfs server for kdump
Version-Release number of selected component (if applicable):
rhev-hypervisor-6.1-8
How reproducible:
Always.
Steps to Reproduce:
1. Enter into rhev-h configuration by type "setup"
2. Configure NFS location for kdump.
3. Enter a nfs address: 10.66.93.179:/var/crash
4. Apply it
Actual results:
It pop a windows say "Invalid NFS Entry".
Expected results:
It is a valid nfs server, no such message displayed.
Additional info:
Screen shot attached.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
A fault in a regular expression causes Kdump to report invalid NFS server addresses for valid NFS servers. A patch for ovirt-node fixes the regular expression and a user can now enter valid NFS servers addresses for Kdump without error.
Created attachment 483111 [details] "Invalid NFS Entry" Description of problem: "Invalid NFS Entry" message display while configure a valid nfs server for kdump Version-Release number of selected component (if applicable): rhev-hypervisor-6.1-8 How reproducible: Always. Steps to Reproduce: 1. Enter into rhev-h configuration by type "setup" 2. Configure NFS location for kdump. 3. Enter a nfs address: 10.66.93.179:/var/crash 4. Apply it Actual results: It pop a windows say "Invalid NFS Entry". Expected results: It is a valid nfs server, no such message displayed. Additional info: Screen shot attached.