Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Insight Orchestration 1.0.1: Release Notes > Chapter 3 Known issues

Interface issues

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

  • If the operating system is not deployed, the operating system information does not display on the Service details page.  If a server or a service is in an UNKNOWN state, an issue has occurred on that server or service. In these situations, Insight Orchestration is able to clean up the database, but might not remove the service or server from the partner domain. If this occurs, the system administrator must clean up the unreachable servers.

  • My Linux server does not list a recently added data disk.  When adding a new data disk to an existing service, if the servers are physical Linux servers or the data disks are added manually (N-Port Id Virtualization is not used), you must reboot the Linux server before the disks are available.

  • I received an error: “ The virtual machine host is not associated with the network ” .  When using a template containing virtual logical servers and network specified by attributes, Insight Orchestration might incorrectly allocate a network and generate an allocation failure message stating, “VM host IP address : The VMHost is not associated with the network subnet, allocated to the logical server.” 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.

  • An Insight Orchestration error appears in HP SIM after a Server Pools timeout.  In HP SIM, the Insight Orchestration error page The HP Insight Orchestration tool cannot be displayed appears when listing server pools exceeds a one-minute timeout.

    This issue can occur when:

    • The physical server or virtual machine Hypervisor is not responding.

    • The Insight Orchestration service is down.

    • The Network is slow or disconnected.

    To resolve this issue:

    • Verify that the physical servers and virtual machine Hypervisors are available

    • Verify that the HP Insight Orchestration service is started.

    • Verify that your network settings are configured correctly.

    • Refresh the Server Pools page.

  • I receive confusing messages when canceling a paused boot disk allocation.  

    When you cancel a boot disk allocation that is in a paused state, Insight Orchestration displays the following messages:

    • Canceled by OOUser ”—The request was canceled by an Administrator through Operations Orchestration Integration.

    • VCDG visible in Storage Prov. Email ”—Canceling information was provided from the Operations Orchestration automated flows.

  • The Request detail message displays disk space as MB instead of GB.  Insight Orchestration displays the units MB and GB as MB. For example, if you request 10 GB of additional storage, the message appears as “ ... 10 MB of disk space. ” The value is correct, however the unit is wrong.

  • Request details displays “ allocated ” whenever a reservation process finishes.  Insight Orchestration displays an “allocated” message when resources are reserved for a provisioning request. If this message appears for a scheduled provisioning operation, the resources are only reserved for the future lease period.

  • Special characters do not validate in Cost units field in Designer.  The Insight Orchestration Designer does not validate the Cost units text field. To avoid displaying unexpected characters, do not enter special characters in the Cost units field when configuring the template.

  • After period of inactivity, my template appears available to edit, until I try to save the template.  The Insight Orchestration Designer session with the Insight Orchestration service has expired. Designer logs you out, but preserves the changes. To save the template, login, recover the modifications, and then save the template.

  • Users might not be able to login to Insight Orchestration after installation or after assigning the user to a different Insight Orchestration group.  A user might not be able to log in to the Insight Orchestration console in HP SIM or the Insight Orchestration self-service portal after installing Insight Orchestration, or after moving the user from oneInsight 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.

  • I cannot log into Insight Orchestration portals after restarting the CMS.  This is an intermittent issue that can occur after a system reboot. In some cases you may not be not able to log into Insight Orchestration portals after a system reboot if the database service, which is required to run the Insight Orchestration service correctly, starts after the Insight Orchestration service. In this case, the Insight Orchestration services will not run correctly. To resolve this issue, verify the database is operational, and then restart the Insight Orchestration service.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2009 Hewlett-Packard Development Company, L.P.