HP Matrix Operating Environment 7.3 Release Notes

Intermittent timeouts may occur during VM deployment
Deploying a VM to a KVM host using Matrix infrastructure orchestration may occasionally time
out with the error:
The request for HP Matrix KVM Private Cloud server <server-name> has
failed. Read timed out connecting to POST.
When this occurs, all hosts on the Matrix KVM Admin Console Hosts screen display an error status.
Suggested action
1. Retry the create service request in Matrix infrastructure orchestration.
2. If the retry does not succeed, perform the following steps:
a. Restart the rabbitmq-server service on the management host by entering the following
command from the command line:
service rabbitmq-server restart
b. Open an SSH connection to the VM host (compute node) and run the following commands
from the command line:
service openstack-nova-compute restart
service openstack-nova-network restart
3. Retry the Create Service request again.
Clear browser cache if upgrade is unsuccessful
If an error occurs during the upgrade to Matrix 7.2 Update 1 KVM Private Cloud, you must clear
your browser's cache to remove partially installed files before retrying the upgrade procedure.
Suggested action
1. Log out of the appliance and close the browser.
2. Clear your browser’s cache:
In Internet Explorer, use ToolsDelete Browsing History.
In Firefox, use ToolsClear Recent History.
3. Log back into the appliance and click Install update from the Settings->Update Appliance
screen to install the patch kit. Reinstalling the pre-update patch kit is not necessary.
Cloud connectivity exclusion ranges cannot include spaces
After an upgrade to Matrix 7.2 Update 1 KVM Private Cloud or an appliance reboot, spaces
inserted between IP addresses in the cloud connectivity exclusion range on the Edit Cloud
Networking screen cause the portion of the range after the space to not appear. This does not
affect IP address assignment; it is an error on the screen only. However, if you want to edit the
range, you are not able to see the current range.
Suggested action
When specifying cloud connectivity exclusion ranges on the Edit Cloud Networking screen, do
not insert a space between IP addresses. For example, specify the following, without a space after
the comma:
192.0.2.1-127,192.0.2.135-254
If a space was inserted before a reboot or upgrade and the exclusion range is not correctly
displayed, manually edit /ci/data/isc-network-info to remove any existing spaces.
48 Issues and suggested actions