Provisioning request for service has paused, Task for logical server failed due to invalid uuid – HP Matrix Operating Environment Software User Manual
Page 152
2.
Perform a manual clean-up process for any affected logical server.
Provisioning request for service has paused
Provisioning request for
allocation is required.
Failure message
This error indicates that insufficient LUNs exist to provision the service.
Possible cause
Create the LUNs and continue provisioning.
Action
Timeout occurs while provisioning storage in a multi-disk request
Timeout occurred while provisioning storage.
Failure message
Submitting a multi-disk request (for example, a logical server group with one server, one private
disk, and one shared disk) takes longer than expected and times out.
Possible cause
Action
1.
In the infrastructure orchestration console Requests tab, delete the paused request.
2.
Edit the timeout.generate.storage.entry property in the infrastructure orchestration
properties file in the default location at C:\Program Files\HP\Matrix infrastructure
orchestration\conf\hpio.properties
.
3.
Increase the default timeout from 25 minutes (1500 seconds) to 60 minutes (3600 seconds).
4.
Edit the spm_timeout property in the logical server management properties file in the default
location at C:\Program Files\HP\Virtual Server Environment\conf\lsa\
lsa.properties
.
5.
Increase the default timeout from 20 minutes (1,200,000 milliseconds) to 40 minutes (2,400,000
milliseconds).
6.
Restart the HP Matrix infrastructure orchestration service.
7.
Restart the HP Logical Server Automation service.
8.
On the Templates tab, select the template and submit a new create service request.
Task for logical server failed due to invalid UUID
Task for logical server
job (ID = …) completed with a failure status. The deployment server does
Failure message
not have the specified system UUID recorded. Deployment Service Connector
cannot confirm the system UUID provided by the caller.
The deployment server cannot bootstrap the server. This issue can occur if the LUN attached to the
server already has an OS deployed to it so that the server is booting from the presented LUN rather
than booting into the designated deployment server.
Possible cause
Action
1.
Locate the Provisioning logical server message that identifies the server blade in use.
2.
Perform a manual clean-up process for any affected logical server. See
152
Troubleshooting