Bug 1289671

Summary:	Calamari installer does not recognize a valid email address
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	bandrus
Component:	Calamari	Assignee:	Christina Meno <gmeno>
Calamari sub component:	Back-end	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	ceph-eng-bugs, flucifre, kdreyer, kurs, wschulze
Version:	1.3.1
Target Milestone:	rc
Target Release:	1.3.4
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-18 08:21:25 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 bandrus 2015-12-08 17:00:40 UTC

Description of problem:
Calamari does not accept an email address that is perfectly valid.

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

How reproducible:
Easily

Steps to Reproduce:
1. Upon user creation, enter an email address in the form of no.dots

Actual results:
Calamari provides the error: Error: "Enter a valid email address."


Expected results:
Calamari should accept an email with dots and dashes

Additional info:
I suspect this is due to the regex that validates email addresses. It should be updated to one that is properly formatted to accept valid email addresses.

Comment 2 Tanay Ganguly 2015-12-16 07:36:09 UTC

I am able to create a user having email address having . (dots) - (Dash) _ (Underscore). This is 1.3.1 Rhel 7.2 setup.


calamari-ctl add_user tanay --password abc --email t.g
calamari-ctl add_user tanay1 --password abcx --email t.g_a-b

Am i missing something.

Is this happening specific to 1.3.0 ?

Comment 3 bandrus 2015-12-17 17:59:29 UTC

I believe we were using 1.3.1, (updated).

The dash is after the @, as described. I am using the web interface, not the CLI.

Comment 7 Christina Meno 2018-01-18 08:21:25 UTC

No customer cases associated with an old bug -- closing this. If you think it still needs fixing feel free to re-open