Cloud bursting with HP CloudSystem Matrix infrastructure orchestration: Matrix-to-Matrix, HP Matrix KVM Private Cloud, HP Cloud Services, and Amazon EC2

The Resource ID matches the Instance ID shown on the cloud provider console (in this example, the AWS Management Console).
Troubleshooting
• You can find useful information in the default location of:
C:\Program Files\HP\Matrix infrastructure orchestration\logs\hpio-controller.log
• You can enable HTTP tracing in the hpio-controller.log file
by following the instructions in the following location, and
then restarting the hpio service.
C:\Program Files\HP\Matrix infrastructure orchestration\conf\log4j.properties
• Use the ioassist command line interface to verify the cloud configuration.
o ioassist -c cloud_pools—Verifies that the cloud capacity pools are specified correctly
o ioassist -c cloud_images—Verifies the cloud capacity pools are configured correctly and communication with the
cloud provider is successful. Use the following troubleshooting instructions for errors resulting from ioassist –c
cloud images.
 “sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find
valid certification path to requested target”
This indicates the cloud provider certificate is not in the trust store. See the "Configure the SSL certificate"
section of this document. Make sure the root certificate from the chain is used (step 3). Make sure the IO
service is restarted after the certificate is added to the trust store.
 “401 Unauthorized”
This indicates the credentials are invalid. For HP Cloud Services, make sure the API secret access key is
used, not the console login password. For Matrix-to-Matrix and HP Matrix KVM Private Cloud, make sure
to use provider.credential.type=password in the pool configuration. In all cases, double check the
configuration steps related to authentication.
 “command: POST https://region-a.geo-
1.identity.hpcloudsvc.com:35357/v2.0/v2.0/tokens HTTP/1.1 failed with
response: HTTP/1.1 405 Method Not Allowed; content: [{"message": {"response"
: "Not Allowed" }}]”
This indicates an incorrect API endpoint is used. For Nova-based providers (Matrix-to-Matrix/HP Matrix
KVM Private Cloud/HP Cloud Services), make sure the version portion of the API endpoint is omitted.
(Notice “v2.0” appears twice, because IO adds a version to the specified endpoint.)
 “Connection timed out”
There are many possible causes. One likely cause is that an HTTP proxy must be used to connect to the
provider. Specify a proxy.host and proxy.port in the cloud capacity pool properties file.
20