Requests and infrastructure services management

Create request fails for my Published template.  When the template is published, the template is validated by the Template Editor. By the time the template is saved, it is valid for publishing. However, if after publishing, any resources are removed from the system (software, networks) the template remains published until it is redesigned, revalidated, and saved in Designer. When changing your environment configuration, be sure to revalidate affected templates to avoid create request failures.

Create request fails with a virtual machine customization error.  If the environment is not completely configured, requests might fail when executing the virtual machine customization step. Issues can include, missing the sysprep folder on the VI3, insufficient licenses on the VI3, or attempting to customize a virtual machine with a guest operating system that is not supported on the VI3. Verify that the environment is correctly configured and be sure you are provisioning a supported guest operating system. For more information on configuration, see Chapter 2 “Getting started”

Request Details displays an error message.  When executing a request, Insight Orchestration might report a failure on the Request Details page. After an error occurs, Insight Orchestration attempts to recover by repeating the tasks or allocation of the resources if the failures are experienced during the provisioning process, or all execute unsuccessfully. During a recovery allocation process, Insight Orchestration uses the Server Pools selected in the initial request.

Create request fails with a "Needs UNSPECIFIED processor architecture" message.  When selecting UNSPECIFIED for a Processor Architecture on a logical server group, Insight Orchestration searches for IA-32 processors. This message refers to UNSPECIFIED, however Insight Orchestration is attempting to utilize IA-32 processors and is not finding sufficient IA-32 servers to fulfill the request and then, displays this message.

Create request fails for with an "internal error" message.  While processing a request, Insight Orchestration reports an "internal error" message, if Insight Orchestration does not find the required resources in the requested environment to fulfill the request. For example, if a network is not configured on Operations Console. For more information on allocation rules, see “Insight Orchestration allocation”.

How do I change lease period for a scheduled request?  You are not allowed to change lease period of a request that is scheduled. Any attempt to the change lease period of such a request fails. To change the lease period of a request that is not started, delete the scheduled request and submit a new request with the updated lease information.

Add data disk request fails.  This error might occur if you attempt to add a data disk for logical servers that are in Standby. To continue to add the data disk, you must initiate a Resume server request, and after restoring the service, add the disks to the Logical Server Group.

A request continues to process after being canceled.  When a request is canceled, Insight Orchestration finishes the ongoing tasks and then cancels the request. No new tasks are started, however tasks in progress must complete to successfully cancel the request.

An infrastructure service is deleted, but I did not delete it.  Insight Orchestration removes infrastructure services when the lease period expires. When an infrastructure service lease period expires and is deleted, My History and Request Details displays a message stating the owner initiated the delete process even though the delete process was triggered by the lease period expiring.

Delete has failed and the environment must be cleaned up manually.  If you a Delete request or Clean up operation fails, you must manually complete the deletion process.

For Virtual logical servers, verify that all the virtual machines and the infrastructure folder name are removed from the VI3. You can locate the Insight Orchestration folder under the virtual machine Host with the same name as the infrastructure provided by the user. Insight Orchestration creates the virtual machines under this folder. If these still exist, you must remove the virtual machines and the infrastructure folder.

For physical logical servers:

When a delete or cleanup operation fails, Insight Orchestration moves the failed servers to the Maintenance pool so you can easily identify the server and fix the issues. After you fix the issues on the server and complete the manual cleanup process, you should reassign the server to the appropriate Insight Orchestration pools using the Insight Orchestration console.

My environment utilizes ESX3i and some template requests fail.  If your environment utilizes ESX3i and Insight Orchestration receives simultaneous requests from the templates of more than 4 virtual ESX3i systems, or simultaneous template requests that contain more than 4 virtual servers, the next request and possibly the original request might fail. To resolve this issue, set the virtual.max.concurrent.requests attribute in the hpio.properties file to 4.