HP Matrix Operating Environment 7.3 Update 1 Release Notes

Provisioning a service may fail when storage volumes in a logical server group
contain different tags
In an Matrix infrastructure orchestration template, different storage tags can be assigned
to the individual volumes in a logical server group. When storage is auto-generated,
each volume is provisioned based on a number of defined requirements, including
these tags. Within a logical server group, if the private data disk(s) contain different
tags than the boot disk, the service will fail to provision.
Suggested action
Use the same storage tags for the boot disk and private data disks in a logical server
group. If separate tags are needed, separate storage pool entries can be manually
defined for the boot disk and private data disks with those separate tags.
Storage auto provisioning does not select a preconfigured data disk if the storage
pool entry does not contain a boot disk
During storage provisioning, if a storage pool entry contains a volume that matches
the requirements of an infrastructure orchestration service, the matching volume is used
for the service.
If the IO template contains a boot disk and a data disk, and the storage pool entry
contains only a boot disk, the boot disk is used and the data disk is automatically
created. However, if the storage pool entry contains only a data disk, the volume is
not used. Both the boot and data disk will be created.
Suggested action
Add a boot disk to the storage pool entry containing the desired data disk, or allow
both disks to be automatically created.
Provisioning errors on Hyper-V cluster after CSV disk failure
If a cluster shared volume (CSV) is in a failed state (for example, if LUNs are not
available or in a read-only state), Insight Control virtual machine management cannot
obtain any information about the CSV. Subsequently, operations on the Hyper-V cluster
(including provisioning) will fail, or all VM hosts in the cluster will be excluded from
operations.
Suggested action
1. Remove the failed CSV from the Hyper-V cluster and correct the issue that caused
the failure.
2. Bring the CSV back online.
3. Manually refresh server resources in Matrix OE visualization by selecting
Tools→Logical Servers→Refresh....
4. Retry the operation.
NIC is not configured properly on a new VM after a successful Linux guest
deployment in an ESX/ESXi/vSphere environment
Networking may not work on a provisioned Linux VM on an ESX/ESXi/vSphere host
due to a known VMware issue that impacts all versions of Linux in an ESX/ESXi/vSphere
environment.
Suggested action
For information about how to reconfigure your network on the provisioned VM, see
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&
cmd=displayKC&externalId=2002767.
32