HP Insight Dynamics 6.2 Release Notes

Erase Hardware job name and service name of a provisioning task must not contain non-English
characters
The following issues may occur if your browser language is set to Japanese.
• If you are using HP Insight Control server deployment on Japanese operating systems and you
specify a Japanese job name for the Erase ProLiant Hardware job, the service is not removed
after physical provisioning.
• If you specify Japanese characters for the service name of a provisioning task, the logical
server is not provisioned.
• If you create a new virtual provisioning template and configure mail settings, the “Approve
or Reject” e-mail contains a garbled service name.
Suggested action 1
1. Launch the Deployment Console.
2. Rename the Erase ProLiant Hardware job to a name that does not contain non-English
characters.
3. Retry the operation.
Suggested action 2
Specify a service name containing valid characters ([a-z] [A-Z] [0-9] [_] [-] [space]).
Suggested action 3
Use the Insight Orchestration Operations Console to approve or reject requests that contain Japanese
characters.
Major issues
Using a remote CMS database with components that use ESA for storage provisioning and server
operations
See “Using a remote CMS database with components that use ESA for storage provisioning and
server operations ” (page 16) for information about an issue that may affect HP Insight Orchestration.
Minor issues
Deployment to a Hyper-V cluster server volume may fail unless the template resides in the
Hyper-V cluster
An HP Insight Orchestration virtual machine deployment to a Hyper-V cluster server volume may
fail when it has reached approximately 60 percent of completion if the source server where the
template resides is not in the Hyper-V cluster. The following error is displayed:
Error deploying Logical Server logical-server-name. Failed to copy all the disk files from source to target
Server. Check the availability of disk space on the target.
Suggested action
Ensure that the source server that contains the template is stored in the Hyper-V cluster before
starting the VM deployment.
Delete service request leaves "clean-me" logical servers when used with Integrity servers
After successfully provisioning an Integrity blade using Ignite-UX, there are manual steps you must
perform to allow the disk to be erased during de-provisioning. Erasing the disk is part of a successful
de-provisioning (delete request) for an Integrity service.
If the disk is not erased, the delete service request may fail and “clean me” logical servers will
remain. In that case, a manual clean-up procedure is required. (See the Suggested action for the
clean-up procedure.)
Before you start a delete request from Insight Orchestration:
HP Insight Orchestration 21