VMware vCloud Usage Meter 4.7.0.1 Release Notes

vCloud Usage Meter 4.7.0.1 \| 26 SEP 2023 \| Build 22497327 Check for additions and updates to these release notes.

vCloud Usage Meter 4.7.0.1 | 26 SEP 2023 | Build 22497327

Check for additions and updates to these release notes.

What's New

The VMware vCloud Usage Meter 4.7.0.1 release provides various bug fixes.

Configuration Maximums

To view the tested scale and the VMware-recommended concurrency limits, see VMware Configuration Maximums.

Product Support Notices

vCloud Usage Meter no longer supports the following functionalities.

registering and managing instances in offline mode
metering of Horizon and Horizon DaaS

Upgrading from Previous Releases

You can install vCloud Usage Meter 4.7.0.1 as an in-place upgrade on top of vCloud Usage Meter 4.3 and later. For information, see Upgrading the vCloud Usage Meter Appliance.

If you are upgrading from vCloud Usage Meter 4.x to version 4.7.0.1, in the vCloud Usage Meter Web interface, you must manually accept the certificates for all metered product servers.

To ensure the automatic aggregation and reporting of the monthly product consumption data, after a successful upgrade from version 4.3 or later to version 4.7.0.1, VMware recommends that you do not revert to the snapshot of the source vCloud Usage Meter appliance.

Resolved Issues

The license edition of VMware Aria Operations in the generated product consumption reports is inaccurate

vCloud Usage Meter 4.7 might provide an inaccurate license edition of VMware Aria Operations and cause a discrepancy in the generated product consumption reports. For example, if the group of virtual machines that are part of the metered VMware Aria Operations instance have Not Licensed, Standard, and Advanced licenses, vCloud Usage Meter should report the instance under the highest license edition from the group - Advanced. However, vCloud Usage Meter might report the instance under the Standard license.
Newly generated support bundle does not contain the archived collectors logs

When you generate a new support bundle, the resulting bundle.tar.gz file does not contain the archived collector log files.
After an upgrade or a fresh deployment of vCloud Usage Meter 4.7, the product consumption data collection for the registered NSX-V instances fails

After an upgrade or a fresh deployment of vCloud Usage Meter 4.7, the product consumption data collection for the registered NSX-V instances fails. As a result, in the vCloud Usage Meter Web interface, the status message of the instances in the NSX-V tab of the Products window is Collection error and you receive a Collection error: NullPointerException notification in the Notifications window. You also observe the NullPointerException error in the collection-nsx-v-error.log and the collection-nsx-v-main.log files.

Known Issues

New - vCloud Usage Meter still reports a deleted customer rule mapped to a VMware Cloud Director instance

A configured and then deleted customer rule mapped to a registered VMware Cloud Director instance is still part of the reported data by vCloud Usage Meter.
Workaround: Execute the following steps.
1. Add a new customer rule.
  1. On the Customer Label page, enter the same name as the name of the deleted rule.
  2. From the Product drop-down menu, select the same VMware Cloud Director endpoint as the endpoint for the deleted rule.
  3. From the Object Type drop-down menu, select Organization.
  4. From Available Objects table, select only System.
2. Wait until the data collection for the VMware Cloud Director instance finishes successfully.
3. Delete the newly added customer rule.
New - Unable to access a newly deployed appliance with deactivated FIPS-compliance mode

When trying to access the Web Interface for a vCloud Usage Meter 4.7.0.1 appliance with deactivated FIPS-compliance mode during the deployment, you encounter a Server Error error message. Also, all the services for the appliance are offline.
Workaround: Execute the following steps.
1. Log in to the vCloud Usage Meter appliance console as usagemeter.
2. Run the following command.
```
fips-util.sh -fn off
```
3. Reboot the vCloud Usage Meter appliance.
New - After upgrading to vCloud Usage Meter 4.7.0.1, an Error in FIPS compliance settings error message appears in the Web interface

If you gradually upgrade vCloud Usage Meter from 4.2 to 4.7.0.1, you might encounter the following error message in the Web interface.

Error in FIPS compliance settings. Please open technical support ticket.

A similar error message appears when trying to enable or deactivate the FIPS-compliance mode in Settings > Security.

FIPS is not configured correctly on the appliance. Click Enable or Disable to resolve it. If the problem persists, raise a technical support ticket.

The issue occurs because the fips parameter has been incorrectly set in the /boot/grub/grub.cfg file during the upgrade.

Workaround: Follow the provided steps in the following KB: https://kb.vmware.com/s/article/96023.
vCloud Usage Meter reports data for the virtual machines of a registered vCenter Server instance after migrating all the virtual machines associated with the instance

If you migrate all the virtual machines associated with a registered vCenter Server instance to another vCenter Server instance, vCloud Usage Meter might still collect and report data for the virtual machines no longer associated with the instance.

Workaround: After you migrate the virtual machines, delete the registered vCenter Server instance from the vCloud Usage Meter Web interface. For more information, see Delete Product Servers in vCloud Usage Meter.
The reported usage of a registered NSX-T Manager instance utilizes the Multi-VC feature

vCloud Usage Meter 4.7.0.1 detects the Multi-VC feature incorrectly and reports product consumption data for the registered NSX-T Manager instance inaccurately. The issue occurs when one or more of the vCenter Server instances are linked with both an IP address and FQDN to the NSX-T Manager instance.

Workaround: Raise a remediation case.
The vmware-um-journal service is in an inconsistent state after configuring, resetting, and re-configuring the local email notifications

After you configure, reset, and then re-configure the local email notifications for a vCloud Usage Meter appliance, the vmware-um-journal service becomes in an inconsistent state.

Follow the workaround provided in the KB: kb.vmware.com/s/article/95721.
vCloud Usage Meter reports data inaccurately for the registered VMware Cloud Director instances that use NSX Advanced Load Balancer with service engine groups tagged as Standard

For VMware Cloud Director versions 10.4.1 and higher, when the registered instances use NSX Advanced Load Balancer with service engine groups that have the Standard feature set, the collected data from vCloud Usage Meter is inaccurate. The issue affects the calculated VMware Cloud Director related usage in the Virtual Machine History report.

Workaround: Follow the workaround provided in the KB article: https://kb.vmware.com/s/article/95046.
Upgrading to vCloud Usage Meter 4.7.0.1 can result in a Failed to process journal=>read error message in the vCloud Usage Meter Web interface

If the host name is incorrectly set when generating the self-signed certificate, upgrading to vCloud Usage Meter 4.7.0.1 results in an error message in the vCloud Usage Meter Web interface.

Failed to process journal=>read. Error:com.vmware.um.common.err.UmException: Hostname localhost not verified: certificate: sha256/t0k44cGiczDyGyzA/xuXcP6arPXzCiYjKeLM0pNG8LU= DN: CN=photon-machine,ST=Some-State,C=US subjectAltNames: []. Check the appliance logs for more details

Also, the Notifications page does not load.

Workaround: Ensure that you set the correct host name. Then you can either generate a new self-signed certificate or import an internal Certification Authority (CA) - Signed Certificate. The certificate CN must match the hostname of the vCloud Usage Meter appliance. For information, see vCloud Usage Meter Certificate Management.
When installing vCloud Usage Meter 4.7.0.1 as an in-place upgrade, the vCloud Usage Meter VM becomes unresponsive

When you attempt to install vCloud Usage Meter 4.7.0.1 as an in-place upgrade, the VM on which you install the new appliance, becomes unresponsive. The process might fail with an error message.

The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes.

Workaround: Follow the steps in the https://kb.vmware.com/s/article/2144053?lang=en_us KB
When editing or auditing a customer rule, all objects that are part of the rule appear as Not Found

If you delete an object from an inventory of a registered vCenter Server instance and that object is part of a customer rule, when editing or auditing the rule, all objects that are part of the rule appear as Not Found. vCloud Usage Meter displays all the selected objects with their MoRef IDs. Moreover, when auditing the rule, all the objects appear in the Missing Target Objects tab even though not all of them are deleted.

Workaround: Edit the customer rule by manually deselecting the deleted objects from the Selected objects list.
Downloading the product consumption data for a vCloud Usage Meter appliance that runs in an offline mode returns an Alert: No usage data to download error message

If a vCloud Usage Meter appliance runs in an offline mode and contains registered product server instances, an attempt to download the product consumption report results in an error message:

Alert: No usage data to download.

The issue occurs when the collected product consumption data is not ready for download yet.

Workaround: Wait for several minutes and then download the product consumption report.
After upgrade to vCloud Usage Meter 4.7.0.1, SSH to the vCloud Usage Meter console results in a WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! error message

After upgrading from vCloud Usage Meter versions 4.3 or 4.4 to this release, when you SSH for the first time to the vCloud Usage Meter console, you receive an error message.

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! This happens because after upgrading, the vCloud Usage Meter host ID is changed in the library.

Workaround: To delete the old host ID, run the following command.

ssh-keygen -R <IP-of-the-UM>
vCloud Usage Meter displays vRealize Operations instead of VMware Aria Operations

As a result of a rebranding, vRealize Operations is now VMware Aria Operations. However, in the vCloud Usage Meter Web interface, the Virtual Machine History, and the Monthly Usage reports, the name is still vRealize Operations.

Workaround: None.
vCloud Usage Meter displays vRealize Network Insight instead of VMware Aria Operations for Networks

As a result of a rebranding, vRealize Network Insight is now VMware Aria Operations for Networks. However, in the vCloud Usage Meter Web interface, the Virtual Machine History, and the Monthly Usage reports, the name is still vRealize Network Insight. The discrepancy in the naming does not affect the metering of the registered VMware Aria Operations for Networks instances.

Workaround: None.
Adding a Tanzu Kubernetes Grid management cluster deployed through Container Service Extension for metering results in a Collection Error: APIError status and notification alert
Adding a Tanzu Kubernetes Grid management cluster deployed through Container Service Extension for metering results in a Collection Error: APIError status. You also recieve a Collection Error: APIError alert in the Notifications tab of the vCloud Usage Meter Web interface. The collection data failure occurs because vCloud Usage Meter does not support the metering of Tanzu Kubernetes Grid management clusters deployed through Container Service Extension.

You might observe the following error in the tkgm_main.log.
```
ERROR --- [TKGM collector thread] c.v.um.tkgmcollector.api.TkgmClient : GET https://ip-address/apis/infrastructure.cluster.x-k8s.io/v1beta1/vspheremachines failed for endpoint '16' with 404
```
Workaround: None.
Creating a customer rule for a registered VMware Cloud Director or a vCenter Server instance before accepting the product certificates results in an Unable to process requests error message

If the status for a registered VMware Cloud Director or a vCenter Server instance is displaying a Please Accept Certificate message and you attempt to create a customer rule for an object on the instance, you receive an error message such as:

Unable to process requests. Error: Failed to get VCD searched objects for VMware Cloud Director.Unable to process requests. Error: Failed to get VC searched objects for vCenter Server.

Workaround: First accept the product certificate and then create the customer rule.
Site Recovery Manager consumption data is missing from the product consumption report

If you configure Storage Profile Protection Groups (SPPG) on a Site Revovery Manager instance, vCloud Usage Meter cannot collect product consumption data from the virtual machines associated with the SPPG.

Workaround: There is no workaround at this time.
vCloud Usage Meter reports twice the product consumption for a re-registered Horizon DaaS instance

If you remove a Horizon DaaS instance from vCloud Usage Meter and re-register it again in the same month, vCloud Usage Meter reports twice the product consumption for this instance.

This happens because Horizon DaaS does not have unique ID and after every registration, the instance is assigned a new ID. As a result, vCloud Usage Meter considers the re-registered Horizon DaaS instance as a new instance.

Workaround: None. After removing a Horizon DaaS instance, if you want to re-register it in the same month, contact VMware Global Support.
vCloud Usage Meter does not send email notifications in case of partial collection failure for vSAN and SRM

vCloud Usage Meter does not send email notifications in case of partial collection failure for vSAN and SRM. Partial collection failure issues are displayed as error messages in the Notifications window of the vCloud Usage Meter Web interface.

Workaround: None.