Bug 1532502 - User automate method stays in 'pending' if user doesn't have email
Summary: User automate method stays in 'pending' if user doesn't have email
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Tina Fitzgerald
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-09 07:11 UTC by Vatsal Parekh
Modified: 2019-02-07 20:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-07 20:14:22 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1530644 0 high CLOSED [Regression] Quota check for users errors out with "no implicit conversion of nil into String" for service provisioning 2021-02-22 00:41:40 UTC

Internal Links: 1530644

Description Vatsal Parekh 2018-01-09 07:11:11 UTC
Description of problem:
According to comments on BZ-1530644, if quota type is set to user and user doesn't have email, request is supposed raise a exception, and can verify this in the automation log.
But this is not showing anything in the request, it stays in 'Pending' forever.
Also, this new email change is not documented as well.

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

How reproducible:


Steps to Reproduce:
1.set quota type to user
2.order a catalog (without assigning an email to the user)
3.

Actual results:
Stays in Pending forever

Expected results:
Should show error or fail when it doesn't have email

Additional info:

Comment 2 Greg McCullough 2018-01-09 14:42:11 UTC
Tina - The concern here is not the need for an email address, but why the request stays in pending.

Comment 3 Tina Fitzgerald 2018-01-09 19:13:46 UTC
Thanks Greg,

Yes, that is an issue.  

An error during the provisioning State Machine causes the request to be updated correctly.  Errors during approval and/or quota processing is not updating the request accordingly.

Thanks,
Tina

Comment 4 Vatsal Parekh 2018-01-16 08:48:46 UTC
Seeing this behavior on 5.8.3.1 as well

Comment 5 Dave Johnson 2018-01-17 21:50:36 UTC
Dropping severity since workaround exists.  Also targeting for 5.9.1 inclusion.

Comment 6 Dayle Parker 2018-02-01 07:30:06 UTC
Would it be possible to add an asterisk to the Email Address field in the UI so it becomes mandatory? 

I'm documenting it in https://bugzilla.redhat.com/show_bug.cgi?id=1534961, but I think a * would be more straightforward.

Comment 7 Dayle Parker 2018-02-01 07:31:26 UTC
Apologies, I meant in the "Adding a new user" field in Comment 6. Thanks all!

Comment 10 Tina Fitzgerald 2019-02-07 20:14:22 UTC
Hi Loic,

Closing since the email is marked as mandatory.

Thanks,
Tina


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