Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1234704

Summary: [RFE] Entering an empty content in Subnet fields does not generate an error
Product: Red Hat OpenStack Reporter: lkuchlan <lkuchlan>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: low Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: aortega, athomas, jschluet, mrunge, nbarcet, yeylon
Target Milestone: betaKeywords: FutureFeature
Target Release: 8.0 (Liberty)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-django-horizon-8.0.0-5.el7ost Doc Type: Enhancement
Doc Text:
Cause: Consequence: Fix: Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 21:02:10 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 lkuchlan 2015-06-23 05:42:34 UTC 
Description of problem:
Entering an empty content in the fields of 'Create Subnet' window, does not generate an error, indicating the necessity to fill the fields 

Version-Release number of selected component (if applicable):
python-django-horizon-2015.1.0-10.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create a Subnet without empty content in the fields
2. Click 'NEXT' 


Actual results:
Nothing happens 

Expected results:
The empty fields should be highlighted in red and an error should be appeared, indicating the necessity to fill the fields
Comment 5 Ido Ovadia 2016-02-01 14:52:18 UTC 
Verified
========
python-django-horizon-8.0.0-10.el7ost.noarch
Comment 7 errata-xmlrpc 2016-04-07 21:02:10 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/RHEA-2016-0603.html