This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

VMware Cloud Provider Lifecycle Manager 1.5 | 18 APR 2023 | Build 21619017 | Download

Check for additions and updates to these release notes.

What's New

VMware Cloud Provider Lifecycle Manager version 1.5 introduces the following new capabilities:

  • Improved task execution

    VMware Cloud Provider Lifecycle Manager 1.5 introduces different capabilities to manage failed tasks. VMware Cloud Provider Lifecycle Manager stores the task payload and you can easily retrieve the task input data.

    When running a task in the VMware Cloud Provider Lifecycle Manager UI, if the task fails, you can restart it without entering the task input data from scratch. For information, see Restart a Task.

    When upgrading a product, if the operation fails, you can either use the automatic rollback or you can resume the upgrade from a specific checkpoint.

    For information about the automatic rollback, see Upgrade a Product by Using the UI.

    For information about how to resume an upgrade from a specific checkpoint, see Resume a product upgrade from a checkpoint.

  • Notifications

    VMware Cloud Provider Lifecycle Manager provides built-in system notifications about activity related to VMware Cloud Provider Lifecycle Manager health and events, such as when a task is completed, when a password and a certificate are about to expire, or when a password and a certicate have expired.

    You can review the notifications in the VMware Cloud Provider Lifecycle Manager UI or you can configure the appliance to send an email to specified recipients. For information, see Managing notifications.

  • Interop reporting

    VMware Cloud Provider Lifecycle Manager allows generating an interoperability product report. The report contains information about the product version, available upgrade versions, as well as related other products and their versions.

    To help you to avoid encountiring issues with expired items, the report contains also information about expiring certificates and passwords.

  • Automatic registration of vCloud Usage Meter with VMware Commerce Portal

    When preparing the vCloud Usage Meter deployment, you can configure the automatic registration of the appliance with VMware Commerce Portal by specifying the CSP token, contract ID, and site name. For information, see the important product considerations in Deploy a Product by Using the UI.

  • Flexible version specification

    VMware Cloud Provider Lifecycle Manager supports defining differently formatted versions for products during deployment or upgrade. The versions can match versions defined by the products in different scenarios, and even can be defined by the product build number.

    In addition, the product files, such as OVA and upgrade package, can be stored anywhere in the \cplcmrepo directory on the VMware Cloud Provider Lifecycle Manager appliance and does not need to be stored in a specific version directory.

  • Registering NSX Advanced Load Balancer

    With VMware Cloud Provider Lifecycle Manager 1.5, you can register an instance of NSX Advanced Load Balancer as a data center component.

Upgrading from Previous Releases

VMware Cloud Provider Lifecycle Manager 1.5 supports an in-place upgrade from VMware Cloud Provider Lifecycle Manager 1.2.x and later.

Documentation

To access the full set of product documentation, go to VMware Cloud Provider Lifecycle Manager Documentation.

Interoperability

For information about the VMware Cloud Provider Lifecycle Manager interoperability with other VMware products, see VMware Product Interoperability Matrices.

Interoperability Bundle Releases

Date

Version Number

Bundle Build Number

Description

28 Sep 2023

1.5.15

22499666

  • Added support for VMware Cloud Director 10.4.2.2

  • Added support for VMware Chargeback 8.10.1

  • Added support for vCloud Usage Meter 4.7.0.1

9 Aug 2023

1.5.14

22199090

Added support for vCloud Usage Meter 4.7.

27 July 2023

1.5.13

22148838

Introducing bug fixes for issues with the VMware Cloud Director upgrade operations.

21 July 2023

1.5.12

22114351

Added support for VMware Cloud Director 10.5

22 June 2023

1.5.11

21960911

  • Added support for VMware Cloud Director 10.4.2.1 and VMware Cloud Director 10.3.3.4.

  • Added a new VMware Cloud Director version format to the list of alternative versions that the interoperability bundle supports.

Resolved Issues

Interoperability Bundle 1.5.11

  • New - VMware Cloud Director operations fail when you configure the same port group and IP addresses for 2 different VMware Cloud Director nodes

    When deploying VMware Cloud Director nodes by using VMware Cloud Provider Lifecycle Manager, you can configure the same port group and IP addresses for two or more VMware Cloud Director nodes. This causes different VMware Cloud Director operations to fail.

  • New - Deploying VMware Cloud Director fails with a NSXT manager is not registered in VCD error message

    When registering VMware NSX with VMware Cloud Director, if the URL for the NSX Manager instance ends with a forward slash ( / ), an attempt to import the same VMware Cloud Director environment in VMware Cloud Provider Lifecycle Manager fails with a NSXT manager is not registered in VCD error message during the post deploy validation.

  • Upgrading VMware Cloud Director fails with an ERROR - Failed to execute task step - Could not create a backup VCD database.. error message

    If you deploy VMware Cloud Director by using VMware Cloud Provider Lifecycle Manager 1.4 and then you upgrade to VMware Cloud Provider Lifecycle Manager 1.5, an attempt to upgrade the existing VMware Cloud Director instance to a later version fails with an error message.

    ERROR - Failed to execute task step - Could not create a backup VCD database..

    No primary DB node defined, cannot create DB backup

  • VMware Cloud Provider Lifecycle Manager lists the incorrect VMware Cloud Director node as the primary node in a database high availability cluster

    If you change the primary node in your VMware Cloud Director database high availability cluster, the discovery fails to detect this change and VMware Cloud Provider Lifecycle Manager continues the consider the initially configured node as the primary one.

Known Issues

  • New - Deploying VMware Cloud Director fails with a NSXT manager is not registered in VCD error message

    When registering VMware NSX with VMware Cloud Director, if the URL for the NSX Manager instance ends with a forward slash ( / ), an attempt to import the same VMware Cloud Director environment in VMware Cloud Provider Lifecycle Manager fails with a NSXT manager is not registered in VCD error message during the post deploy validation.

    Workaround:

    1. In VMware Cloud Director, remove the slash ( / ) from the URL for the NSX Manager instance.

    2. In VMware Cloud Provider Lifecycle Manager, import the VMware Cloud Director environment.

  • New - Upgrading from VMware Cloud Director 10.4.1 to a later version fails

    When you attempt to upgrade VMware Cloud Director 10.4.1 to a later version, during the upgrade of the database phase, the operation fails with a The status of DB cluster is unavailable or not healthy error message.

    This is happening because when VMware Cloud Provider Lifecycle Manager starts the upgrade of the next cell, the update of the database to postgres version 14 is not yet completed.

    Workaround:

    1. Configure the waiting time between the completion of a node upgrade and starting to upgrade the next node to 180 seconds .

      su -c "echo 'CPLCM_VCD_UPGRADE_WAIT_AFTER_UPDATE=180' >> /etc/environment"

    2. Restart the vcplcm-api service.

      sudo systemctl restart vcplcm-api.service

  • New - Redeploying of a VMware Cloud Director node in a database high availability cluster fails

    In the VMware Cloud Provider Lifecycle Manager UI, when you attempt to redeploy a VMware Cloud Director node that resides in a database high availability cluster, the operation fails.

    Workaround:

    1. Unregister the failed cell. For information, see Unregister a Failed Primary or Standby Cell in a Database High Availability Cluster in the VMware Cloud Director documentation.

    2. In the VMware Cloud Provider Lifecycle Manager UI, restart the failed task.

  • New - Deploying VMware Chargeback (formerly vRealize Operations Tenant App for VMware Cloud Director) fails with a Could not update root password for vROPS TA machine error message

    When you deploy VMware Chargeback by using the VMware Cloud Provider Lifecycle Manager UI, the operation fails with an error message.

    Could not update root password for vROPS TA machine

    This happens because VMware Cloud Provider Lifecycle Manager cannot set the root password for the VMware Chargeback appliance after deploying it.

    Workaround:

    1. In vCenter Server, login to the VM console of the VMware Chargeback appliance and manually set the root password.

      Note: Do not delete the VMware Chargeback VM from vCenter Server.

    2. By using the VMware Cloud Provider Lifecycle Manager UI, restart the deployment of VMware Chargeback.

  • New - Upgrading VMware Cloud Director fails with an ERROR - Failed to execute task step - Could not create a backup VCD database.. error message

    If you deploy VMware Cloud Director by using VMware Cloud Provider Lifecycle Manager 1.4 and then you upgrade to VMware Cloud Provider Lifecycle Manager 1.5, an attempt to upgrade the existing VMware Cloud Director instance to a later version fails with an error message.

    ERROR - Failed to execute task step - Could not create a backup VCD database..

    No primary DB node defined, cannot create DB backup

    Workaround: After upgrading to VMware Cloud Provider Lifecycle Manager 1.5, run a discovery on the VMware Cloud Director instance.

    After running the discovery, if upgrading the VMware Cloud Director instance fails again, rollback and start the upgrade again.

  • Upgrading vCloud Usage Meter 4.4 to a later version fails with an Operation timed out error message

    If you use VMware Cloud Provider Lifecycle Manager to upgrade vCloud Usage Meter 4.4 to a later version, the upgrade might fail with an error message.

    Failed to upgrade Usage Meter appliance. Command output: Operation timed out.

    Workaround: Resume the upgrade by using checkpoint 1 or rollback and start the upgrade process from the beginning.

  • Resuming a cancelled VMware Cloud Director upgrade from a checkpoint fails

    If you initiate a VMware Cloud Director upgrade and you cancel the task before it completes, resuming the upgrade process from a checkpoint fails.

    The log file displays an Error while retrieving information for DB cluster health: error message.

    Workaround: To complete the product upgrade, you can resume by using an earlier checkpoint or rollback and start the upgrade process from the beginning.

  • After configuring vRealize Operations Tenant App 8.6 or 8.6.1 with VMware Cloud Director, the vRealize Operations Manager UI is not visible in VMware Cloud Director

    After you configure vRealize Operations Tenant App 8.6 or 8.6.1 with VMware Cloud Director 10.3.x, the vRealize Operations Manager UI might not be visible in VMware Cloud Director.

    Workaround:

    You must upload the vRealize Operations Tenant App plug-in to your VMware Cloud Director Service Provider Admin Portal.

    1. From the /opt/vmware/plugin directory on the vRealize Operations Tenant App appliance, copy the plugin.zip file locally to your machine.

    2. Log in to your VMware Cloud Director Service Provider Admin Portal and upload the plug-in file. For information, see Upload a Plug-in in the VMware Cloud Director Service Provider Admin Portal Guide documentation.

    3. Log off and log in to your VMware Cloud Director Service Provider Admin Portal.

  • The VAMI displays the VMware Cloud Provider Lifecycle Manager health status as Unknown

    After upgrading VMware Cloud Provider Lifecycle Manager, the Summary page of the VAMI displays the appliance health status as Unknown.

    Workaround: Restart the VMware Cloud Provider Lifecycle Manager appliance.

  • Upgrading to VMware Cloud Director 10.4.1 fails with a Timeout error message

    Using the VMware Cloud Provider Lifecycle Manager UI, when you attempt to upgrade to VMware Cloud Director 10.4.1, the upgrade process fails with a Timeout error message.

    This happens when the upgrade timeout setting is set to its default value of 30 minutes.

    Workaround: Change the upgrade timeout setting.

    1. Log in to the VMware Cloud Provider Lifecycle Manager console.

    2. Change the environment variable for the timeout setting by running the command.

      su -c "echo CPLCM_VCD_UPGRADE_PROCESS_TIMEOUT={timeout_value_in_minutes} >> /etc/environment; systemctl restart vcplcm-api.service"

      You are prompted for the root password.

  • Updating an existing deployment of vRealize Operations Tenant App 2.5.x, 2.6.x, or 8.6.x fails

    When you use VMware Cloud Provider Lifecycle Manager to update an existing vRealize Operations Tenant App 2.5.x, 2.6.x, or 8.6.x deployment, the REST API task fails with an ERROR status.

    Workaround:

    1. In vCenter Server, open the vRealize Operations Tenant App VM console.

    2. Manually update the root password for vRealize Operations Tenant App to match the password you configure in the VMware Cloud Provider Lifecycle Manager REST API request. 

    3. In VMware Cloud Provider Lifecycle Manager, run the update REST API request.

  • Deployment and upgrade tasks for vRealize Operations Tenant App can take a long time to complete or fail with an error message

    In VMware Cloud Provider Lifecycle Manager, when you try to deploy or upgrade vRealize Operations Tenant App, the API task can take a long time to complete or fail with an error message such as:

    ERROR

    Vrops TA service or VM tools did not start successfully on VM

    Workaround:

    1. In vCenter Server, open the vRealize Operations Tenant App VM console.

    2. Restart the vRealize Operations Tenant App virtual machine. 

    3. In VMware Cloud Provider Lifecycle Manager, run the deploy REST API request.

Interoperability Bundle 1.5.12

  • Deploying VMware Cloud Director 10.5 fails with a No VCD API version can be retrieved error message

    When deploying VMware Cloud Director 10.5, if you do not configure the REST API or VMware Cloud Director Tenant Portal certificates, the deployment task fails at the CONFIGURE_PRODUCT step with an error message.

    No VCD API version can be retrieved. Probably the public address endpoint is not accessible, please make sure the load balancer (if applicable) is properly configured and works with current VCD server ciphers

    Workaround:

    1. Update the load balancer to accept TLS 1.2 with the ciphers defined by VMware Cloud Director 10.5. For information, see Supported Security Protocols and Cipher Suites in the VMware Cloud Director 10.5 Release Notes.

    2. In VMware Cloud Provider Lifecycle Manager, restart the deployment task.

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