Hide Forgot
Description of problem: Create a quota with decimal numbers, message shows like: Invalid value: "100m": must be an integer It's correct for CPU, but not for other resources. Version-Release number of selected component (if applicable): openshift v1.1.4-274-g1b00abe kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 How reproducible: Always Steps to Reproduce: 1. Create a project # oc new-project qwang1 2. Apply quota with decimal numbers to a project # cat quota-d.yaml apiVersion: v1 kind: ResourceQuota metadata: name: quota-d spec: hard: cpu: "0.20" memory: "1.5Gi" persistentvolumeclaims: "0.10" pods: "0.10" replicationcontrollers: "0.20" resourcequotas: "0.1" secrets: "0.10" services: "0.5" # oc create -f quota-d.yaml -n qwang1 --config=/home/openshift.local.config/master/admin.kubeconfig Actual results: 2. [root@ip-172-18-3-170 home]# oc create -f quota-d.yaml -n qwang1 --config=/home/openshift.local.config/master/admin.kubeconfig The ResourceQuota "quota-d" is invalid. * spec.hard[resourcequotas]: Invalid value: "100m": must be an integer * spec.hard[secrets]: Invalid value: "100m": must be an integer * spec.hard[services]: Invalid value: "500m": must be an integer * spec.hard[persistentvolumeclaims]: Invalid value: "100m": must be an integer * spec.hard[pods]: Invalid value: "100m": must be an integer * spec.hard[replicationcontrollers]: Invalid value: "200m": must be an integer Expected results: It's better to give messages like this: * pods: invalid value '0.10', Details: must be an integer Additional info:
I will look to see if we can preserve the format from input.
No movement on this in 3 years. If issues still persist in 4.x, please open a new bug.