License expiry date displays one day earlier than expected in VMware Aria Operations
search cancel

License expiry date displays one day earlier than expected in VMware Aria Operations

book

Article ID: 429347

calendar_today

Updated On:

Products

VCF Operations VCF Operations/Automation (formerly VMware Aria Suite) VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

Administrators may observe a discrepancy in the license expiry date displayed within the VMware Aria Operations (formerly vRealize Operations) user interface.

  • The Administration > Management > Licensing or Subscriptions > Legacy Licenses page shows the license expiry date as one day prior to the actual entitlement date (e.g., 20/10/2028 instead of 21/10/2028).

  • The Broadcom Support Portal confirms the license key is valid until the correct date (e.g., 21/10/2028).

  • Other products using the same key, such as VMware Aria Operations for Logs (vRealize Log Insight), display the correct expiry date.

Cause

This issue occurs when the license key is applied to the Aria Operations appliance while the appliance system time is set to a non-UTC timezone (e.g., GMT+8).

The application interprets the expiration timestamp relative to the local appliance time, causing the date to be rendered as the preceding day in the User Interface.

Resolution

RESOLUTION

To rectify the displayed expiry date, the appliance timezone must be standardized to UTC, and the license must be re-applied.

  1. Prepare the Cluster

    • Log in to the Admin UI (https://<master-node-fqdn>/admin).

    • Click Take Offline to bring the cluster offline.

    • Once offline, log in to the vSphere Client and take a snapshot of all Aria Operations nodes to ensure a rollback point.

  2. Update Timezone to UTC

    • Log in to the Primary node via SSH as root.

    • Run the following command to set the timezone to UTC:

          timedatectl set-timezone UTC

       

    • Repeat this step on all nodes in the cluster (Primary Replica, Data, and Remote Collectors).

  3. Restart the Cluster

    • Reboot the cluster nodes following the standard shutdown and startup sequence.

    • Once the nodes are back online, verify the timezone is set to UTC on all nodes by running:

          timedatectl

  4. Re-apply the License

    • Log in to the Aria Operations Product UI.

    • Navigate to Administration > Management > Licensing.

    • Select the license key showing the incorrect date and click Delete (or Remove).

    • Click Add License and re-enter the same license key.

    • Verify that the expiry date now reflects the correct entitlement date (e.g., 21/10/2028).

  5. Finalize Configuration

    • Bring the cluster back Online via the Admin UI.

    • Optional: If a specific local timezone is required for operational reasons, the timezone can be reverted after the license has been successfully re-applied and validated.

Additional Information

 

 

Powered by Wolken Software