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

Bug 1511291

Summary: Adding negative value to resource quota yaml file while Setting Limits for Users and Projects.
Product: OpenShift Container Platform Reporter: kavitha <kavithanidi>
Component: ocAssignee: Fabiano Franz <ffranz>
Status: CLOSED DUPLICATE QA Contact: Xingxing Xia <xxia>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: aos-bugs, 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-11-09 05:48:35 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 kavitha 2017-11-09 05:33:22 UTC
Description of problem:
Adding negative value to resource quota yaml file while Setting Limits for Users and Projects: while creating quota where persistent volume claim given with negative values 
I could execute the command successfully without any error.

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.6.173.0.48-1.git.0.1609d30.el7.noarch

How reproducible:
resource-quota.yaml

apiVersion: v1
kind: ResourceQuota
metadata:
  name: core-object-counts
spec:
  hard:
    configmaps: "10"
    persistentvolumeclaims: "-4"
    replicationcontrollers: "20"
    secrets: "10"
    services: "10"


Steps to Reproduce:
1.login to Openshift CLI 
2.oc create -f resource-quota.yaml


Actual results:
It is successfully executing and creating quota.

Expected results:
It should throw the error after detecting the negative value

Additional info:

Comment 1 kavitha 2017-11-09 05:48:35 UTC

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