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

Bug 863459

Summary: Proper validation messages required while adding new user with blank fields.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED NOTABUG QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: dajohnso
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-10 14:46:03 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:
Attachments:
Description Flags
msg header none

Description Aziza Karol 2012-10-05 13:59:44 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Login to conductor as admin.
2.Navigate to Administer->users.
3.Add new  user by keepinh all the fields blank.
  
Actual results:
No username, email and password entered and it displays:
"Username is too short (minimum is 1 character)
Email is invalid
Password is too short (minimum is 4 characters)"

see attached screenshot.


Expected results:
When no username, email and password entered, message like "username, email and password" cannot be blank should be displayed.

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-0.13.16-1.el6cf.noarch
aeolus-conductor-doc-0.13.16-1.el6cf.noarch
aeolus-all-0.13.16-1.el6cf.noarch
rubygem-aeolus-cli-0.7.3-1.el6cf.noarch
aeolus-configure-2.8.8-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.16-1.el6cf.noarch
Comment 1 Aziza Karol 2012-10-05 14:01:12 UTC 
Created attachment 622237 [details]
msg header
Comment 3 Dave Johnson 2012-10-10 14:46:03 UTC 
The validation is in place... field to short, etc