Bug 867832

Summary: remove the validation when the object is blank
Product: Red Hat Enterprise Linux 6 Reporter: Guohua Ouyang <gouyang>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4CC: acathrow, bsarathy, chchen, chetan, cshao, gouyang, hadong, huiwa, jboggs, leiwang, mburns, moli, ovirt-maint, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.5.0-12.el6 Doc Type: Bug Fix
Doc Text:
Previously, activating and then leaving a field without any input would cause a popup saying "Invalid Entry". Now, if the field is empty, the error does not appear.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 16:41:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Guohua Ouyang 2012-10-18 11:53:26 UTC
Description of problem:
Current, when move over the Kdump ssh/nfs location on TUI, it will report "Invalid entry" even it's blank. it's very boring to confirm such a warning when user did not input anything.
which also happens on NFSv4, RHN URL and CA.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121015.1.el6

How reproducible:
100%

Steps to Reproduce:
1. move over the Kdump ssh/nfs location on TUI without any input
 

Actual results:
It report "Invalid ssh enrty" or similar.

Expected results:
No "Invalid" window pop up.

Comment 2 Mike Burns 2012-10-19 15:36:25 UTC
http://gerrit.ovirt.org/8679

Comment 11 errata-xmlrpc 2013-02-28 16:41:02 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-2013-0556.html