Bug 1710914

Summary: [UI] Empty Network name error should be improved
Product: OpenShift Container Platform Reporter: Ilanit Stein <istein>
Component: Console Kubevirt PluginAssignee: Rastislav Wagner <rawagner>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aos-bugs, cnv-qe-bugs, gouyang, mlibra, ncredi, rawagner, sgordon
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.0.0-14.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-24 20:16:06 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 Ilanit Stein 2019-05-16 14:36:56 UTC 
Description of problem:
In Create VM dialog, provision source: Import,
Network screen, picking an Empty Network Name,
will display in the Network field "Empty Network Name" in red.

However, since putting Empty Network name, actually blocks the option to proceed on to the next screen (Storage Screen),

I think it would be better to put "Network Name cannot be empty",
to better describe the problem, and reflect that this problem is the cause,
it is not possible to proceed. 

Version-Release number of selected component (if applicable):
hco tag: v.2.0.0-12
Comment 1 Rastislav Wagner 2019-05-20 10:38:48 UTC 
https://github.com/kubevirt/web-ui-components/pull/466
Comment 2 Marek Libra 2019-06-03 10:00:54 UTC 
Included in kubevirt-2.0.0-14.6 .
Will be in hco-bundle-registry:v2.0.0-22 .
Comment 5 errata-xmlrpc 2019-07-24 20:16:06 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://access.redhat.com/errata/RHEA-2019:1850