Created attachment 1416316 [details]
Screenshot of error messages
Description of problem: When creating a new user with a mismatched password, incorrect "Name/Userid can't be blank" message is also delayed
How reproducible: 100%
Steps to Reproduce:
1. Create a user and fill out the name, userid and group fields. Input a password and enter a different password for "Confirm Password". Attempt to Save the user
Actual results: Errors for "Password/Verify Password do not match￼" is valid but the additionnal error messages for "Password can't be blank", "Name can't be blank" and "Userid can't be blank" are invalid and should not be shown
Expected results: Only the message for mismatched password should be displayed
Additional Info: Failing to add the user to a group also shows the error "Password can't be blank"
New commit detected on ManageIQ/manageiq-ui-classic/master:
Author: Zita Nemeckova <firstname.lastname@example.org>
AuthorDate: Wed Apr 4 03:33:25 2018 -0400
Commit: Zita Nemeckova <email@example.com>
CommitDate: Wed Apr 4 03:33:25 2018 -0400
Get all user form data before validating for errors per field
app/controllers/ops_controller/ops_rbac.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
*** Bug 1598140 has been marked as a duplicate of this bug. ***
VERIFIED in 220.127.116.11. During new user creation, attempting to create a new user with a mismatched password but all other fields were valid resulted in only the invalid password message when saving the user. Saving the user with valid matching passwords but missing a group, username and/or full name correctly displayed the error message for the invalid field
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.
*** Bug 1656458 has been marked as a duplicate of this bug. ***