HP Matrix Operating Environment 7.3 Release Notes

Suggested action
Note the number of hosted VM instances when evaluating whether resources on a particular host
are available. If sufficient resources are not available, perform one of the following tasks:
• Add compute resources to the host.
• Free space on the host by deleting existing instances that are no longer needed.
External yum repository can cause host activation to fail
An external yum repository, used for RPM-based Linux updates, that is enabled on a VM host can
cause the first attempt to activate the host to time out and display “<Host> activation failed. Error:
Failed to configure user accounts on remote host.”
Suggested action
Retry activating the host. After the first failed attempt, subsequent attempts to activate the host will
proceed as expected. To avoid this circumstance, disable all external yum repositories by logging
into the VM host to be activated and setting enabled=0 for the file /etc/yum.repos.d/
rhel.repo.
Filtering the Instances screen for “Resize pending” requires manual cleanup
On the Matrix KVM Admin Console Instances screen, filtering for instances in the “Resize pending”
state adds the characters state:Resize%20pending to the search field. When this occurs,
subsequent filtering for instances in any state does not return results.
Suggested action
Erase all characters in the search field, then enter state:Resize pending in the search field.
Incorrect message is displayed when filtering or searching returns no results
If you filter or search for resources on a Matrix KVM Admin Console screen, the message is a
hyperlink to create resources or take corrective action. The link is unnecessary because there are
no resources to display based on the filter options.
Suggested action
Ignore the message. Clear the search text and search for a known string that produces results, for
example “source”.
HP Matrix Operating Environment infrastructure orchestration
Enabling Matrix infrastructure orchestration provisioning support of Linux VMs on
Hyper-V
NOTE: The hpio.properties value
skip.linux.on.hyperv.template.personalization allows Linux VMs on Hyper-V, but
it is deprecated. See “Skipping automated OS customization” (page 50) for information on allowing
Linux VMs on Hyper-V.
Skipping automated OS customization
By default, after infrastructure orchestration deploys an OS to a server, it automatically customizes
(personalizes) the OS by setting the host name, IP addresses, netmask, default gateway, and other
attributes as appropriate. As of the 7.3 release, automatic OS customization can be skipped by
performing the actions noted below. These actions allow the service template architect to design
service templates that use OS images intended to be customized outside of Matrix OE, such as
when deploying Linux VMs onto Hyper-V. When the skip customization feature is used, customization
of the deployed VM is no longer performed by Matrix, and becomes the responsibility of the
architect to ensure that the VM is configured properly.
50 Issues and suggested actions