Example error condition - Duplicate clone name

A provisioner has given a name that is already in use to a VMware clone.

  1. vCenter detects the error and sends the contents of the error message to the ServiceNow instance.
  2. The system stops the workflow and creates a catalog task for the provisioner in the Cloud Operations Portal.

    This task shows that a requested instance named global-by-1 has generated an error.

  3. The provisioner opens the task and attempts to identify the error. The description shows that global-by-1 is a duplicate name.
  4. The provisioner then opens the original request by clicking the link in the Request item field.
  5. The provisioner enters a unique name for the virtual machine and then clicks Update. The catalog task appears.
  6. The provisioner clicks Close Task and the Cloud Operations Portal appears. The task now shows a state of Closed.
  7. The workflow resumes and checks the new clone name with vCenter.
  8. vCenter approves the name, and provisioning continues.