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.
An error code was displaying in the ping test results page when the input host length was more than 64 characters. This no longer occurs as there is now a check for the length of each field as well as the entire hostname to make sure it is not too long. It adds a validator for length, which checks for total length of less than 256 octets and field lengths of less than 64 octets.
Created attachment 758482[details]
ping
Description of problem:
Error code show in ping test results page when input host length are more then 64 characters.
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130528.0.el6_4
ovirt-node-2.5.0-17.el6_4.5.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install RHEV-H and configure network.
2. Enter network ping test page.
3. Enter a long host to ping(more then 64 characters).
Actual results:
1. Failed with error code 5 show in ping test results page when input host length are more then 64 characters.
Expected results:
Pop-up "name too long" or provide limit.
Additional info:
1. No such issue if the host length less then 64 characters.
(In reply to Fabian Deutsch from comment #2)
> The FQDNOrIPAddress validator should probably be fixed to check for to long
> hostnames.
Yes, but it's 63 chars *per level*. So we need to split on . and check each section.
test-really-really-really-really-really-long-hostname.test-really-really-really-really-really-long-hostname.example.com is perfectly fine (54 chars in the first 2 levels)
This is fixed in http://gerrit.ovirt.org/#/c/15583/
It adds a validator for length which checks for total length of less than 256 octets and field lengths of less than 64 octets.
This is fixed in http://gerrit.ovirt.org/#/c/15583/
It adds a validator for length which checks for total length of less than 256 octets and field lengths of less than 64 octets.
rhev-hypervisor6-6.5-20131017.0
ovirt-node-3.0.1-4.el6.noarch
Test steps:
1. Install RHEV-H and configure network.
2. Enter network ping test page.
3. Enter a long host to ping(more then 64 characters).
Test result:
"The field must contain members of 63 characters or less" will pop-up.
So the bug is fixed, change bug status to 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
Thanks in advance.
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
Created attachment 758482 [details] ping Description of problem: Error code show in ping test results page when input host length are more then 64 characters. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130528.0.el6_4 ovirt-node-2.5.0-17.el6_4.5.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H and configure network. 2. Enter network ping test page. 3. Enter a long host to ping(more then 64 characters). Actual results: 1. Failed with error code 5 show in ping test results page when input host length are more then 64 characters. Expected results: Pop-up "name too long" or provide limit. Additional info: 1. No such issue if the host length less then 64 characters.