I'd like to confirm this is a VCD bug or just my misunderstanding. Details are listed as below.
VCD info
- VCD version: 5.5.2
- VCenter 5.5.0
- VMware ESXi, 5.1.0
Issue summary
- 400 Bad requrest returned when disabling an OrgVDC via VCD API just after having an insufficient memory error.
- The ovdc was disabled even if 400 was returned.
- Could disable another org vdc which is under the same condition from VCD API GUI without error.
- Reproducible
Details
I saw a weird phenomenon. This is reproducible and here's the steps.
- Create an org vdc (Allocation pool).
- Increase it's memory size to enough big size like 1000GB to exceed physical memory limit intentionally using VCD API. (This task will fail.)
- Then try to disable the org vdc via VCD API.
Here's the log message when I tried to do No.3.
=============================
Sent Request: POST https://<IP>/api/admin/vdc/e568c924-e1a1-4758-857b-b223b4ef0e26/action/disable
Accept: application/*+xml;version=5.5
X-Vcloud-Authorization: <authorization code>
Got response: HTTP/1.1 400 Bad Request
Date: Thu, 05 Jun 2014 16:43:18 GMT
Date: Thu, 05 Jun 2014 16:43:59 GMT
Vary: Accept-Encoding
Content-Length: 16202
Content-Type: application/vnd.vmware.vcloud.error+xml;version=5.5
Client-Date: Thu, 05 Jun 2014 16:43:28 GMT
Client-Peer: <IP>:443
Client-Response-Num: 4
Client-SSL-Cipher: AES256-SHA
<?xml version="1.0" encoding="UTF-8"?>
<Error xmlns="http://www.vmware.com/vcloud/v1.5" stackTrace="com.vmware.vcloud.api.presentation.service.BadRequestException: There are insufficient memory resources to complete the operation. Please contact the System Administrator.
:
=============================