Description of problem: When trying to add Quota from CLI , auto complete does not suggest name parameter although it is mandatory ( see Additional Parameter ) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: add quota --datacenter-identifier [RHEVM shell (connected)]# add quota --datacenter-identifier 5febe649-9fc2-4f76-8d2b-01fa3b88baac error: status: 400 reason: Bad Request detail: Quota [name] required for add ## When adding name parameter I get another error ( will file separate busy for this issue ) [RHEVM shell (connected)]# add quota --datacenter-identifier 5febe649-9fc2-4f76-8d2b-01fa3b88baac --name quotatest error: status: 500 reason: Internal Server Error detail: JBWEB000065: HTTP Status 500 - java.lang.NullPointerException
Quota has no implemented API, and in 3.3 you will not be able to use "add quota". This will be handled in the next version as a part of bug 893927.
Suggesting for to be included in 3.5.
Currently the RESTAPI has limited support for quota. There are quota resources, like /datacenter/{datacenter:id}/quotas, but they are read only. This has probably changed since this bug was reported, but today the quota isn't presented as an alternative in autocompletion for the "add" command, and if typed manually it generates a reasonable error message: [RHEVM shell (connected)]# add quota --datacenter-identifier 00000002-0002-0002-0002-000000000117 ==================================== ERROR ================================= no such action "add" ============================================================================ Same if the --name parameter is added: [RHEVM shell (connected)]# add quota --datacenter-identifier 00000002-0002-0002-0002-000000000117 --name myquota ==================================== ERROR ================================= no such action "add" ============================================================================ Once the quota support is implemented in the RESTAPI and the SDK is regenerated these commands will work correctly, without any change to the CLI. I suggest to close this bug as fixed in the current version, or as a duplicate of bug 893927.
Closing as duplicate, based on comment 3. *** This bug has been marked as a duplicate of bug 893927 ***