HTTP 405 Method Not Allowed Error When Modifying VDC Resource Allocations in VMware Cloud Director
search cancel

HTTP 405 Method Not Allowed Error When Modifying VDC Resource Allocations in VMware Cloud Director

book

Article ID: 394984

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • When attempting to modify CPU or memory allocations for an Organisation VDC via the Cloud Director UI or API, a 405 HTTP Method Not Allowed error is returned.
  • In the Developer Tools of your browser, under the Network tab, you will see a stack trace containing:
com.vmware.vcloud.api.presentation.service.impl.VdcServiceAdapterImpl.validateVdcNotLocked(VdcServiceAdapterImpl.java:2671)

Environment

VMware Cloud Director

Cause

  • This error may occur if the VDC is locked by a stale busy_object in the system database.
  • The lock prevents resource modifications through the VCD interface.

Resolution

Important: Before performing any changes in the database, ensure a full backup is taken and change procedures are followed.

  1. Identify the affected VDC’s UUID:

    select id from org_prov_vdc where name = 'VDC_NAME_HERE';


  2. Take that UUID and check for stale locks:

    select * from busy_object where object_id = 'xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx';


  3. If confirmed, delete the lock:

    delete from busy_object where object_id = 'xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx';

     

Impact: Once the stale busy_object entry is cleared, the VDC should no longer be locked, and resource updates can proceed normally.

Additional Information

Powered by Wolken Software