Cannot start VMs due to a Bad Request error in VMware Cloud Director
search cancel

Cannot start VMs due to a Bad Request error in VMware Cloud Director

book

Article ID: 418261

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • When attempting to power on a vApp, an error similar to the following occurs:

    Bad Request: Error occurred in the backing network provider: The object path=[/infra/tier-1s/########-####-####-####-############] cannot be deleted as either it has children or it is being referenced by other objects path=[/infra/segments/########-####-####-####-############], error code 500030

Environment

VMware Cloud Director 10.6.x

Cause

VMware Cloud Director (VCD) is attempting to remove an existing T1 before powering on the vApp, but the underlying NSX is unable to comply due to the existence of an attached network segment that is outside of the control of VCD.

Resolution

Remove the segment referenced in the underlying NSX environment and attempt powering on the vApp once more.