Bug 1506827
| Summary: | Round number pod quotas are treated incorrectly | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Steven Walter <stwalter> |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
| Status: | CLOSED DUPLICATE | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.1 | CC: | aos-bugs, jforrest, jokerman, mmccomas |
| 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-10-30 18:41:48 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: | |||
This appears to be have the same underlying cause as https://bugzilla.redhat.com/show_bug.cgi?id=1413516 |
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"