Bug 1466641 - ResourceQuota doesn't support limits.storage
ResourceQuota doesn't support limits.storage
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2017-06-30 02:53 EDT by Kenjiro Nakayama
Modified: 2017-08-22 21:18 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kenjiro Nakayama 2017-06-30 02:53:21 EDT
Description of problem:
- ResourceQuota doesn't support limits.storage.

Version-Release number of selected component (if applicable):
- OCP 3.x

How reproducible:
- 100%

Steps to Reproduce:
1. Define ResourceQuota with limits.storage

  [root@knakayam-ose33-master1 ~]# cat b.yaml 
  apiVersion: v1
  kind: ResourceQuota
    name: core-object-counts
      limits.storage: "10Gi"

2. Create ResourceQuota

  # oc create -f b.yaml 

Actual results:

] # oc create -f b.yaml 
The ResourceQuota "core-object-counts" is invalid.

* spec.hard[limits.storage]: Invalid value: "limits.storage": must be a standard resource type or fully qualified
* spec.hard[limits.storage]: Invalid value: "limits.storage": must be a standard resource for quota

Additional info:
- Red Hat explicitly included it in the docs - https://github.com/openshift/openshift-docs/pull/3729

Description of problem:

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:
Comment 1 Derek Carr 2017-06-30 09:40:22 EDT
unlike cpu or memory, storage is not a burstable resource.

as a result, we only support requests.storage as a quota resource name.

this is an error in the documentation.

pr for doc is opened here:

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