vCloud Usage Meter 4.6 | 04 OCT 2022 | Build 20554128

Check for additions and updates to these release notes.

What's New

The VMware vCloud Usage Meter 4.6 release introduces the following:

Configuration Maximums

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

Supported Browsers

The vCloud Usage Meter 4.6 Web application is compatible with the following Web browsers.

  • Google Chrome

  • Mozilla Firefox

  • Microsoft Edge

vCloud Usage Meter 4.6 is tested against the following Web browser versions.

Windows 11

  • Google Chrome 104.0.5112.102

  • Microsoft Edge (64-bit) 104.0.1293.70

  • Mozilla Firefox 91.13.0esr

macOS Monterey 12.4

  • Google Chrome 105.0.5195.102

  • Apple Safari 15.5 (17613.2.7.1.8)

  • Mozilla Firefox (64-bit) 104.0.1

centOS 7

  • Google Chrome 105.0.5195.125

centOS 8

  • Mozilla Firefox 104.0.2

Upgrading from Previous Releases

You can install vCloud Usage Meter 4.6 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.6, 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.6, VMware recommends that you do not revert to the snapshot of the source vCloud Usage Meter appliance.

Resolved Issues

  • The Cluster History report does not contain the metered product consumption data for vSAN Cloud Native Storage

    If the vSAN Cloud Native Storage feature for a registered vCenter Server instance is not in a vSphere with Kubernetes/ Tanzu environment, the Cluster History report does not contain the product consumption data for the respective vSAN Cloud Native Storage.

  • The Monthly Usage report contains metered data for vSAN license editions that are different from the expected ones

    For vCenter Server/vSAN versions 7.0 and above, if the vSAN cluster in a registered vCenter Server instance uses one of the Shared Witness or the Stretched Cluster features, the Monthly Usage report contains metered data for vSAN license editions that are different from the expected ones.

    Also, the number of the features associated with the cluster in the vsanFInt column of the Cluster History report is incorrect.

  • After upgrading to vCloud Usage Meter 4.5, vCloud Usage Meter stops metering Site Recovery Manager

    After upgrading to vCloud Usage Meter 4.5, the metering of the registered Site Recovery Manager instance fails. The vCloud Usage Meter log files displays the following error message.

    Unknown Failure HTTP transport error: org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46) ::

Known Issues

  • New - When installing vCloud Usage Meter 4.6 as an in-place upgrade, the vCloud Usage Meter VM becomes unresponsive

    When you attempt to install vCloud Usage Meter 4.6 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

  • Upgrading to vCloud Usage Meter 4.6 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.6 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.

  • 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.

  • The status of the registered NSX-V Manager instance is Credentials verified

    The Credentials verified message appears in the Status column of the registered NSX-V Manager instance.

    Workaround: None. The status changes to OK in an hour.

  • 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.

  • 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.

  • 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.

  • After upgrade to vCloud Usage Meter 4.6, 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: From the known_hosts file, delete the old host ID, and accept the new one.

    1. Log in to the vCloud Usage Meter console as root.

    2. Open the known_hosts file for editing by using a text editor such as vi.

      vi /etc/known_hosts

    3. Delete the old host ID.

    4. Save the /etc/known_hosts file.

      :wq!

    5. SSH to the vCloud Usage Meter console and confirm the connection to the host ID.

check-circle-line exclamation-circle-line close-line
Scroll to top icon