Bug 1394558

Summary:	Show notification for the user when tenant quota is exceeded.
Product:	Red Hat CloudForms Management Engine	Reporter:	Aziza Karol <akarol>
Component:	Automate	Assignee:	William Fitzgerald <wfitzger>
Status:	CLOSED ERRATA	QA Contact:	Anurag <ansinha>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	jhardy, mfalesni, mkanoor, obarenbo, tfitzger
Target Milestone:	GA
Target Release:	5.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	quota
Fixed In Version:	5.8.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-31 14:23:27 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 Aziza Karol 2016-11-13 14:21:48 UTC

Description of problem:


Version-Release number of selected component (if applicable):
5.7.0.10-beta3.20161109111947_9a61b18 

How reproducible:
100%

Steps to Reproduce:
1.create a new tenant and enforce the quota on this tenant such that it should reached its set enforcement level.
2.create a user with the above tenant.
3.login with the above user and provision

Actual results:
No notifications if the tenant quota is reaching its quota enforcement level.

Expected results:
Should show notifications to the user if tenant quota is reached.

Additional info:

Comment 2 William Fitzgerald 2017-01-04 20:33:26 UTC

see PR: https://github.com/ManageIQ/manageiq/pull/12370

Comment 3 Milan Falešník 2017-03-14 13:48:50 UTC

Verified in 5.8.0.4: After submitting a provision request that goes over quotas I get a notification.

Comment 5 errata-xmlrpc 2017-05-31 14:23:27 UTC

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.

https://access.redhat.com/errata/RHSA-2017:1367