Bug 1506827 - Round number pod quotas are treated incorrectly
Summary: Round number pod quotas are treated incorrectly
Keywords:
Status: CLOSED DUPLICATE of bug 1413516
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-26 21:57 UTC by Steven Walter
Modified: 2021-06-10 13:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-30 18:41:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steven Walter 2017-10-26 21:57:20 UTC
Description of problem:
When using a round number, pod quota is shortened (i.e. 1000 -> 1k), but this is consequently treated as "1", chopping off the k.

Version-Release number of selected component (if applicable):
3.3, 3.4. Unconfirmed in 3.5. Fixed by 3.6

How reproducible:
Confirmed

Steps to Reproduce:
1. Create a quota:

apiVersion: v1
kind: ResourceQuota
metadata:
  name: compute-resources
spec:
  hard:
    pods: "1000" 

2. Scale a deployment from 1 to 2


Actual results:
"Quota limit reached"

Expected results:
I expect about 999 more pods to be schedulable

Additional info:
I thought a bug was opened on this and fixed for 3.6 but I cannot locate it using search terms "openshift pod quota"

Comment 2 Samuel Padgett 2017-10-30 12:13:14 UTC
This appears to be have the same underlying cause as

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


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