Bug 1176057 - Can not setup hostname as 63 characters with non FQDN format
Summary: Can not setup hostname as 63 characters with non FQDN format
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-3.6.0-rc3
: 3.6.0
Assignee: Douglas Schilling Landgraf
QA Contact: wanghui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-19 10:10 UTC by wanghui
Modified: 2016-03-09 14:24 UTC (History)
9 users (show)

Fixed In Version: ovirt-node-3.3.0-0.4.20150906git14a6024.el7ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 14:24:29 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0378 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update for RHEV 3.6 2016-03-09 19:06:36 UTC
oVirt gerrit 36305 0 master MERGED defaults: use the same hostname validators as valid Never

Description wanghui 2014-12-19 10:10:19 UTC
Description of problem:
It can not setup the hostname as 63 charters with non FQDN format. It will report an error like follows.
================================================================================
An error appeared in the UI: <InvalidData u'The field must contain members of 63 characters or less.'>
Press ENTER to logout ...
or enter 's' to drop to shell
================================================================================

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.0-20141218.0.el7ev
ovirt-node-3.1.0-0.37.20141218gitcf277e1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. TUI Install rhev-hypervisor7-7.0-20141218.0.el7ev
2. Setup hostname as follow format.
   Hostname: sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

Actual results:
1. After step2, it will report as follows.
================================================================================
An error appeared in the UI: <InvalidData u'The field must contain members of 63 characters or less.'>
Press ENTER to logout ...
or enter 's' to drop to shell
================================================================================

Expected results:
1. It should accept it without error.

Additional info:
1. No such issue when setup hostname with non FQDN format less than 63 chars.

Comment 1 Douglas Schilling Landgraf 2014-12-19 12:54:11 UTC
(In reply to wanghui from comment #0)
> Description of problem:
> It can not setup the hostname as 63 charters with non FQDN format. It will
> report an error like follows.
> =============================================================================
> ===
> An error appeared in the UI: <InvalidData u'The field must contain members
> of 63 characters or less.'>
> Press ENTER to logout ...
> or enter 's' to drop to shell
> =============================================================================
> ===
> 
> Version-Release number of selected component (if applicable):
> rhev-hypervisor7-7.0-20141218.0.el7ev
> ovirt-node-3.1.0-0.37.20141218gitcf277e1.el7.noarch
> 
> How reproducible:
> 100%
> 
> Steps to Reproduce:
> 1. TUI Install rhev-hypervisor7-7.0-20141218.0.el7ev
> 2. Setup hostname as follow format.
>    Hostname: sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
> 
> Actual results:
> 1. After step2, it will report as follows.
> =============================================================================
> ===
> An error appeared in the UI: <InvalidData u'The field must contain members
> of 63 characters or less.'>
> Press ENTER to logout ...
> or enter 's' to drop to shell
> =============================================================================
> ===
> 
> Expected results:
> 1. It should accept it without error.
> 
> Additional info:
> 1. No such issue when setup hostname with non FQDN format less than 63 chars.

Hello  wanghui,

I cannot reproduce this report, for me every time I add sssssss (more then 63 chars) appear a message 'The field must contain a field less then 64 chars or an empty string' and the save button is disabled. Am I missing any step?

Thanks!

Comment 2 Douglas Schilling Landgraf 2014-12-19 14:07:14 UTC
Removing needinfo on ycui as couldn't reproduce as well.

Comment 3 Ying Cui 2014-12-19 14:41:02 UTC
(In reply to Douglas Schilling Landgraf from comment #2)
> Removing needinfo on ycui as couldn't reproduce as well.

re-read hui's description, I can reproduce this issue now.

my steps:
1. ssh to login rhevh
2. _63_ characters, if you enter 62 s, you can not encounter this issue. 
3. then "Save"

the error happen:
An error appeared in the UI: <InvalidData u'The field must contain members of 63 characters or less.'>
Press ENTER to logout ...
or enter 's' to drop to shell

Comment 4 Huijuan Zhao 2015-07-29 07:14:11 UTC
re-read hui's description, I also reproduce this issue now.

How reproducible:
100%

my steps:
1. TUI Install RHEV-H 6.7-20150728.0.e16ev
2. Setup hostname with 64 characters as follow format.
Hostname: 1234567890123456789012345678901234567890123456789012345678901234

the error happen:
An error appeared in the UI: <InvalidData u'The field must contain members of 63 characters or less.'>
Press ENTER to logout ...
or enter 's' to drop to shell

Comment 6 wanghui 2015-10-26 07:31:07 UTC
Test version:
rhev-hypervisor7-7.2-20151025.0.el7ev
ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch

Test steps:
1. TUI Install rhev-hypervisor7-7.2-20151025.0.el7ev
2. Setup hostname with 63 chars as follow format.
   Hostname: sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

Test result:
1. The hostname with 63 characters can be saved succeed.

So this bug is fixed in ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch. Change the status to Verified.

Comment 8 errata-xmlrpc 2016-03-09 14:24:29 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.

https://rhn.redhat.com/errata/RHBA-2016-0378.html


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