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.
Bug 720956 - UI: Hostname can't begin with Arabic number in Network page.
Summary: UI: Hostname can't begin with Arabic number in Network page.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.2
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 730201 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-13 10:56 UTC by cshao
Modified: 2016-04-26 16:40 UTC (History)
6 users (show)

Fixed In Version: ovirt-node-2.0.2-0.7.gitb88a4ee.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 19:17:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
invalid hostname (24.57 KB, image/jpeg)
2011-07-13 10:56 UTC, cshao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1783 0 normal SHIPPED_LIVE rhev-hypervisor6 bug fix and enhancement update 2011-12-06 15:10:54 UTC

Description cshao 2011-07-13 10:56:14 UTC
Created attachment 512631 [details]
invalid hostname

Description of problem:
Hostname can't begin with Arabic number in Network page.

Version-Release number of selected component (if applicable):
rhev-hypervisor-6.2-0.5.el6

How reproducible:
100%

Steps to Reproduce:
1. Enter Network page, set hostname to Arabic number (e.g. 123).
2. Press tab button.
3. Please see attachment for more details.
  
Actual results:
Invalid hostname when configuration check. 
But can set hostname begin with Arabic number in command line.

Expected results:
Hostname can begin with Arabic number in Network page.

Additional info:

Comment 8 Alan Pevec 2011-08-12 21:13:31 UTC
*** Bug 730201 has been marked as a duplicate of this bug. ***

Comment 11 cshao 2011-08-31 10:16:13 UTC
I am not sure why the hostname should include at least alphabet?

Comment 12 Alan Pevec 2011-09-08 10:15:28 UTC
(In reply to comment #11)
> I am not sure why the hostname should include at least alphabet?

It can be numbers only, http://tools.ietf.org/html/rfc1123#page-13
"Don't use digits at the beginning of the name." recommendation is from rfc1178 but that rfc is information only, not a standard.

Comment 13 Guohua Ouyang 2011-09-14 02:10:59 UTC
according to comment #12 "It can be numbers only“, hence assign the bug back.

Comment 14 Joey Boggs 2011-09-14 13:21:32 UTC
changed https://bugzilla.redhat.com/show_bug.cgi?id=661594#c17

Comment 18 errata-xmlrpc 2011-12-06 19:17:45 UTC
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-2011-1783.html


Note You need to log in before you can comment on or make changes to this bug.