HP Matrix Operating Environment 7.3 Release Notes

Major issues
RHEL 6.4 with KVM OS Build Plan fails with error
The default Insight Control server provisioning RHEL 6.4 KVM OS build plan configures the “br0”
device, causing post-installation customization to fail with the following error:
Error customizing Logical Server <Logical server name> realized by
<target UUID>.
Suggested action
To prevent this, edit the kickstart file referenced in the OS Build Plan as follows.
1. Remove the “br0” device configuration by removing the section delineated between the
comments “BEGIN KVM BRIDGE CONFIGURATION” and “END KVM BRIDGE
CONFIGURATION.”
2. In the %post section of the kickstart file, add the chkconfig NetworkManager off
command as shown below:
%post --log /tmp/icsp-networkconfig.log
chkconfig NetworkManager off
Deployment using the above methods will result in error messages appearing in the Insight Control
server provisioning jobs. Specifically, you will see BRDC write personalization task output that
contains entries similar to the following:
BRDC read personalization task for server <server number>
Invalid eth name vibr0
These messages are expected and can be ignored.
Minor issues
Error deploying a KVM private cloud may create an additional, incomplete virtual machine instance
Deploying a KVM private cloud using Matrix OE may, in rare situations, return the following error
in the Matrix infrastructure orchestration Requests Details:
Task for Logical Server <logical server name> has failed. Logical server job (ID = <server ID>) completed with
a failure status. Failure: Could not create HP Matrix KVM Private Cloud server <logical server name> in capacity
pool isc: 413
Request Entity Too Large The body of your request was too large for this server.
When this error is displayed, the service is created successfully. However the Matrix KVM Admin
Console Instances screen shows one virtual machine in addition to the number of virtual machines
requested in the service template. This instance will have an error status.
Suggested action
In the Matrix KVM Admin Console, delete the extra instance that was created with an error status.
If you subsequently attempt to delete the infrastructure service without first deleting this instance,
the delete service request will fail.
OS type of virtual machine instances are “not set” after restart
After restarting the Matrix KVM Private Cloud appliance, the OS type of existing virtual machine
instances is displayed as “not set” on the Instances screen.
Suggested action
Expand the details of the instance and note the image name. From the Images screen, search for
the image name. The OS type of the image is shown, which is also the OS type of the instance.
Matrix KVM Private Cloud 47