Bug 1347158 - UX: Error message too vague when creating new automate domain / namespace / object
Summary: UX: Error message too vague when creating new automate domain / namespace / o...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.7.0
Assignee: mkanoor
QA Contact: Milan Falešník
URL:
Whiteboard: ui:ux:automate:flash_msg
Depends On:
Blocks: 1372768
TreeView+ depends on / blocked
 
Reported: 2016-06-16 07:53 UTC by Jan Krocil
Modified: 2017-03-17 09:21 UTC (History)
8 users (show)

Fixed In Version: 5.7.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1372768 (view as bug list)
Environment:
Last Closed: 2017-01-11 20:28:14 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Krocil 2016-06-16 07:53:28 UTC
Description of problem:
SSIA

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

How reproducible:
Always

Steps to Reproduce:
1. Automate > Add a New Domain
2. Enter "My Domain" as name
3. Click "Add"

Actual results:
Error message "Name is invalid".

Expected results:
Error message "Name is invalid (only ASCII alphanumeric characters allowed, no spaces)" or something similar. If we know what we expect, we might as well tell the user.

Additional info:
This applies to all the objects under Automate. Multiple flash messages should be fixed.

Comment 3 Harpreet Kataria 2016-06-24 15:44:58 UTC
Flash error message displayed on the screen is coming from model code. Controller is calling .valid? method on domain/namespace record https://github.com/ManageIQ/manageiq/blob/master/app/controllers/miq_ae_class_controller.rb#L1326, and displaying error message returned from that call.

~Harpreet

Comment 7 Milan Falešník 2016-09-29 12:58:38 UTC
Verified in 5.7.0.1. I received a message stating the allowed characters in the name.


Note You need to log in before you can comment on or make changes to this bug.