Bug 797747 - A little problem of error message of new console page.
Summary: A little problem of error message of new console page.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
: 798389 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-27 08:18 UTC by Yujie Zhang
Modified: 2015-05-15 01:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:31:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
sshkey error message (66.27 KB, image/png)
2012-02-27 08:18 UTC, Yujie Zhang 		no flags Details
application name error message (20.29 KB, image/png)
2012-02-27 08:19 UTC, Yujie Zhang 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Yujie Zhang 2012-02-27 08:18:32 UTC 
Created attachment 565984 [details]
sshkey error message

Description of problem:

A little problem of error message of new console page.

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

devenv_1642

How reproducible:always


Steps to Reproduce:
1.Go to app/accont page
2.Try to add a new key without key type
3.
  
Actual results:

Error message will came out:

"Type Type is required and cannot be blank."

Expected results:

Is it the "Type" word duplicate or we miss a ":"? Details see in attachment.

Additional info:

Please also check this issue on app/console/applicatios page.
Comment 1 Yujie Zhang 2012-02-27 08:19:07 UTC 
Created attachment 565985 [details]
application name error message
Comment 2 Clayton Coleman 2012-02-27 15:27:32 UTC 
Same is a duplicate, error messages need to not prefix the field since they are coming from the server.
Comment 3 Xiaoli Tian 2012-02-29 05:51:35 UTC 
*** Bug 798389 has been marked as a duplicate of this bug. ***
Comment 4 Clayton Coleman 2012-02-29 05:55:08 UTC 
I cleaned up the message aggregation a bit.  We should go back next sprint and make the error messages more clear (because this is a tricky place where users can screw up, and showing two separate messages isn't very helpful).
Comment 5 Yujie Zhang 2012-03-20 04:54:23 UTC 
Verify this bug on stage, it has been fixed now, thanks.
Note You need to log in before you can comment on or make changes to this bug.