HP Insight Orchestration 6.0 User Guide

deployment job within the same folder, and then modify the Erase ProLiant ML/DL/BL Array
Configuration {LinuxPE} job. For more information on modifying the job, see “Creating server deployment
job folders”.
An infrastructure service has been deleted, but I did not delete it.Issue
Insight Orchestration may be configured to remove infrastructure services when the lease period expires. When
an infrastructure service lease period expires and the service is deleted, My History and Request Details displays
Possible cause
a message stating the owner initiated the delete process even though the delete process was triggered by the
lease period expiring.
You can be notified one week, and then one day, in advance by email that a lease is set to expire and that the
service will be deleted. To use this option, your email address must appear in the Operations Orchestration
Action
System Property: HpioNotificationRecipients. Use Operations Orchestration Studio to set this
configuration parameter.
A delete request has failed. The environment must be manually cleaned.Issue
—Possible cause
For virtual logical servers, Insight Orchestration creates a folder under the virtual machine Host with the same
name as the infrastructure service provided by the user. This folder contains all the folders and files corresponding
to the virtual logical servers. Delete this folder and all its contents.
Action
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, perform a manual cleanup process for the affected logical servers. See “Manual
clean-up process”.
Virtual
Troubleshooting items addressed in this section:
• Allocation failed. VM host <IP address> : The VMHost is not associated with the network <subnet Id>,
allocated to the logical server.
• Could not find a provisioned infrastructure service with the specified logical server in Insight
Orchestration.
In some circumstances, when processing a create request for a template containing a network specified by
attributes and a virtual logical server group, Insight Orchestration may be unable to successfully reserve resources
even though they exist.
Issue
There is not a specific failure message for this issue, and the problem will surface as a server reservation failure
message. The issue applies only to virtual logical servers.
Insight Orchestration performs subnet allocation prior to server allocation. Consider the following case:Possible cause
Two subnets (Subnet1, Subnet2) match LogicalSubnetA.
Subnet1 is associated with VmHost1 and no others.
Subnet2 is associated with VmHost2 and no others.
Based on subnet allocation criteria, Subnet1 is the best choice for LogicalSubnet A.
However, if VmHost1 is unsuitable for the LogicalServerGroups associated with LogicalSubnetA, the reservation
will fail without Subnet2 being evaluated. VmHost1 might be unsuitable because it is not recoverable or it has
an insufficient number of processors, in which case the following server reservation error message would appear;
"Reservation failed for logical server SvrGrp1-1. Unable to find a virtual server
with the following requirements: Recoverable. 3 processor(s)."
To resolve this issue, narrow the network selection options, eliminating general specifications (“Any” options)
from the network selection attributes. If removing all general options does not select the correct network, specify
the network by name or select fewer server pools and resources when submitting the request.
Action
From the Insight Dynamics logical server perspective, clicking on the Manage this logical server with HP
Insight Orchestration icon displays the following message: Could not find a provisioned
Failure message
infrastructure service with the specified logical server in Insight Orchestration.
If a physical server was selected and the infrastructure service was provisioned
by Insight Orchestration, check if its status is not standby.
The logical server had been deactivated.Possible cause
68 Troubleshooting