HP Insight Orchestration 6.0 User Guide

A user might not be able to log in to the Insight Orchestration console in Systems Insight Manager or the Insight
Orchestration self-service portal after installing Insight Orchestration, or after moving the user from one Insight
Action
Orchestration user group to another, for example moving a user from the HPIO_Administrators to the HPIO_Users
group. To resolve this issue, reboot the CMS.
When extending the lease period, the operation fails without stating a specific reason or error message.Issue
Insufficient resourcesPossible cause
If you attempt to extend the lease period of an infrastructure beyond the period available to its resources
(insufficient static IP addresses or insufficient capacity on a virtual machine host), the Insight Orchestration
Action
displays an error message, stating “ The informed lease period conflicts with another
infrastructure service lease period and cannot be updated. ” Verify that there are sufficient
and available:
• Static IP addresses
• Virtual machine memory resources
• Disk resources
An operation on servers under a VCDG did not complete the requested operation.Issue
Server not managed by Virtual Connect Enterprise ManagerPossible cause
Virtual Connect Domain Group status must display managed by Virtual Connect Enterprise Manager for Insight
Orchestration to correctly execute operations over its resources.
To perform maintenance activities on a Virtual Connect Domain that is managed by Virtual Connect Enterprise
Manager and prevent Insight Orchestration from attempting to use a physical server that is not available when
the VCDG is under maintenance, you must:
Action
1. Access the Insight Orchestration console and select the Server Pools tab.
2. Move the physical servers in the VCDG to the maintenance pool.
3. Access Virtual Connect Enterprise Manager and perform the required steps to complete the desired operation.
4. In Insight Orchestration, move the physical servers from the maintenance pool back to the appropriate server
pools to make them available for use in Insight Orchestration.
Moving servers to the Maintenance pool always deactivates the servers.Issue
—Possible cause
When you move a server to the Maintenance pool, that resource is deactivated. A warning displays stating
that services reserving the server for future use will be canceled, and current logical servers using the resource
Action
will be deactivated. When moving a server to the Maintenance pool, you can attach a note to the server that
indicates why the server was moved to maintenance.
The memory resources allocated to a virtual machine host are not available after I use the Deactivate servers
operation.
Issue
When virtual infrastructures or individual servers are deactivated, Insight Orchestration does not recognize the
memory previously allocated to the logical servers as available to allocate to other virtual machines.
Possible cause
—Action
A step in the Request Details is shown as having failed.Issue
—Possible cause
When executing a request, Insight Orchestration might report the failure of one or more steps on the Request
Details page. After such an error occurs, Insight Orchestration attempts to recover by retrying the tasks or
Action
re-allocating the resources. During a recovery allocation process, Insight Orchestration uses the server pools
selected in the initial request. If a step fails too many times, the whole request fails. The number of retries is a
Insight Orchestration configurable property.
A request continues to process after being canceled.Issue
Current task in progressPossible cause
When a request is canceled, Insight Orchestration has to allow the ongoing tasks in the managed environment
to complete. No new tasks are started, however all in progress tasks must complete before the request can be
canceled.
Action
Role specific operations 71