Logo
Help Center

Knowledge Base: An order in vCenter fails to cancel and eventually fails to remove the VDC in the vCenter.

Rahul Sarkar -

Error Message in UI - Portal-2015-01-26-000236:vmwareVsphere:java.lang.IllegalArgumentException: entity must not be null.

 

Root Cause Analysis:

--------------------------------------------------------------------------------------------------------------------------------------

  1. If the vdc_id (i.e. resource pool ID for the specific VDC) in the table vsphere_user_order_vdc found in the EAS Database does not match with the ID found for that resource group from Managed Object Browser in vCenter, the order might fail to cancel and will fail to remove the VDC as well.
  2. This mismatch might occur if the resource pool is deleted from the vCenter Native portal manually and the same is created again using a script. As a result the resource pool will be created having exactly the same parameters but this time the resource pool ID for that specific VDC will be different than the vdc_id stored in the table vsphere_user_order_vdc found in EAS database.

Remedy:

--------------------------------------------------------------------------------------------------------------------------------

  1. In the EAS Database, manually update the column vdc_id (i.e. resource pool ID for the specific VDC) in the table vsphere_user_order_vdc with the resource pool ID found in the Managed Object Browser in vCenter for that concerned resource pool. This will map the EAS database table vsphere_user_order_vdc with the updated resource pool ID.
  2. Retry cancelling the order from the portal. The order will get cancelled and will eventually delete the resource pool in vCenter.

 

N.B: To avoid such scenario in the future, kindly do not delete any resource pool manually from the vCenter native portal which are provisioned from EAS.

Have more questions? Submit a request

Comments

Powered by Zendesk