Bug 1198990 - UI crash when setting hostname with illegal format
Summary: UI crash when setting hostname with illegal 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
high
high
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Douglas Schilling Landgraf
QA Contact: wanghui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 09:42 UTC by wanghui
Modified: 2016-03-09 14:17 UTC (History)
10 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:17:08 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 None None None Never
oVirt gerrit 38950 0 master MERGED valid: add to FQDNOrIPAddress, HostnameLength validation Never

Description wanghui 2015-03-05 09:42:15 UTC
Description of problem:
The UI will crash when setting hostname with the illegal format like " hostname.test". It will report the error like follows.
================================================================================
An error appeared in the UI: <InvalidData u'The field must contain an empty string or a valid FQDN or a valid IPv4 address or a valid IPv6 address.'>
Press ENTER to logout ...
or enter 's' to drop to shell
================================================================================

Version-Release number of selected component (if applicable):
rhevh-7.1-20150304.0.el7ev.iso
ovirt-node-3.2.1-9.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H 7.1.
2. Change the hostname to " hostname.test" and save

Actual results:
1. After step2, it will report error like follows.
================================================================================
An error appeared in the UI: <InvalidData u'The field must contain an empty string or a valid FQDN or a valid IPv4 address or a valid IPv6 address.'>
Press ENTER to logout ...
or enter 's' to drop to shell
================================================================================

Expected results:
1. After step2, it should report the format of the hostname is illegal with more friendly way.

Additional info:

Comment 1 cshao 2015-03-09 07:43:31 UTC
I can reproduce this issue on RHEV-H 3.5.z for RHEV 6.6  rhev-hypervisor6-6.6-20150304 build.

Test version:
RHEV 6.6  rhev-hypervisor6-6.6-20150304
ovirt-node-3.2.1-9.el6.noarch

Comment 2 Douglas Schilling Landgraf 2015-03-18 00:51:59 UTC
Hi wanghui and shaochen,

(In reply to shaochen from comment #1)
> I can reproduce this issue on RHEV-H 3.5.z for RHEV 6.6 
> rhev-hypervisor6-6.6-20150304 build.
> 
> Test version:
> RHEV 6.6  rhev-hypervisor6-6.6-20150304
> ovirt-node-3.2.1-9.el6.noarch

Could you please re-test using the latest isos? I cannot reproduce this error in the below versions:

rhev-hypervisor6-6.6-20150312.0
rhev-hypervisor7-7.1-20150312.0


Thanks!

Comment 9 wanghui 2015-10-28 06:11:44 UTC
Test version:
rhev-hypervisor7-7.2-20151025.0.el7ev
ovirt-node-3.3.0-0.18.20151022git82dc52c.el7ev.noarch

Test steps:
1. Install rhev-hypervisor7-7.2-20151025.0.el7ev
2. Change the hostname to " hostname.test" 

Test result:
1. After step2, it prompts that "The field must contain a vaild IPv4 address or a valid IPv6 address or a valid FQDN and a field less than 64 chars or an empty string". 
2. It can not save the illegal format hostname.

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

Comment 11 errata-xmlrpc 2016-03-09 14:17:08 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.