Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1445890

Summary: Creating a project horizon gui display error unable to set project quotas
Product: Red Hat OpenStack Reporter: bigswitch <rhosp-bugs-internal>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED DUPLICATE QA Contact: Ido Ovadia <iovadia>
Severity: low Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: aortega, athomas, berrange, dasmith, eglynn, kchamart, mrunge, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 12:46:26 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 bigswitch 2017-04-26 17:37:36 UTC 
Description of problem:
When creating a new project, horizon gui will display an error: unable to set project quotas popup

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

How reproducible:
100%

Steps to Reproduce:
1. Login to Horizon
2. Create a new project


Additional info:
This is seen in horizon log

==> /var/log/horizon/horizon.log <==
2017-04-26 17:33:18,435 613881 WARNING horizon.exceptions Recoverable error: gigabytes must be an integer. (HTTP 400) (Request-ID: req-19e3e7b9-9f4f-4843-9820-d9386a0d30bc)
Comment 1 Artom Lifshitz 2017-04-28 12:37:28 UTC 
I'm going to recategorise this bug to Horizon, since it doesn't appear that Nova is involved at any point.

Pure speculation from my part, as a Nova and not Horizon engineer - but it looks like a non-integer value was entered into a field that only accepts integers, and perhaps Horizon isn't handling that error condition very well.
Comment 2 Radomir Dopieralski 2017-04-28 12:46:26 UTC 

*** This bug has been marked as a duplicate of bug 1414997 ***