Bug 1300788

Summary: Quota limits for tenant does not work as expected
Product: Red Hat CloudForms Management Engine Reporter: Pavol Kotvan <pakotvan>
Component: ProvisioningAssignee: William Fitzgerald <wfitzger>
Status: CLOSED ERRATA QA Contact: Pavol Kotvan <pakotvan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: jhardy, jprause, obarenbo, pakotvan
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: tenant_cfme:quota
Fixed In Version: 5.6.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 15:32:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 4 Shveta 2016-01-27 19:43:07 UTC
Assigning to add test case

Comment 5 William Fitzgerald 2016-01-28 15:01:14 UTC
Pavol,

Can you please provide the EVM and Automation logs.
Can you please also provide the appliance information ?

Thanks

Bill

Comment 8 William Fitzgerald 2016-01-29 16:42:08 UTC
More info in BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=1289278

Comment 9 William Fitzgerald 2016-02-05 20:57:00 UTC
Pavol,

I can't get into your appliance.  Is the IP you supplied still good and is it started ?

Please let me know ...

Thanks

Billy

Comment 11 William Fitzgerald 2016-02-11 19:38:04 UTC
Pavol,

I was able to get into your appliance.  I couldn't figure out the password for
User tenant1 so I created another account (User Billy with same password as smartvm) for the tenant1 tenant.  I was able to re-create the problem with memory and storage not being checked thru quota. 

More info in BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=1289278

please see PR:

https://github.com/ManageIQ/manageiq/pull/6381

I believe this will fix the problem ....

Billy

Comment 14 errata-xmlrpc 2016-06-29 15:32:14 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/RHBA-2016:1348