VMware Cloud Provider Lifecycle Manager 1.4 | 28 OCT 2022 | Build 20686879

Check for additions and updates to these release notes.

What's New

The VMware Cloud Provider Lifecycle Manager 1.4 introduces the following:

  • Simplified Product Registration

    You can register existing product deployments by using a simplified registration method. This requires you to provide a limited number of connection details for the product. VMware Cloud Provider Lifecycle Manager then attempts to discover all necessary environment details. At a later stage, you can complete the registration by providing any missing environment information, such as specific passwords and node details. For information, see Register an Existing Instance with VMware Cloud Provider Lifecycle Manager.

  • Capability for Day-2 Operations by Using the UI

    With this release, the UI supports day-2 operations, such as product upgrade, certificate management, and node management thus allowing you to perform all necessary operations from a single user interface.

  • Parallel Task Processing

    With VMware Cloud Provider Lifecycle Manager 1.4, you can initiate multiple management tasks simultenously. If the tasks are not operating on the same product deployment, the appliance runs them concurrently. For information, see Configure the Maximum Number of Threads VMware Cloud Provider Lifecycle Manager Can Run in Parallel.

  • Capability to check and install new interoperability bundles

    By using the VMware Cloud Provider Lifecycle Manager API or the graphical user interface, you can check for new interoperability bundles that are available for download.

    If an interoperability bundle is available, you can use a direct link to download the bundle. You can then upload the bundle and install it directly by using the UI or the API.

    For information, see Update the Appliance by Using an Interoperability Bundle.

  • Capability to generate support bundles and view more task details

    By using the user interface, you can view more task details, such as information about executed steps and detailed logs.

    In addition, you can generate a support bundle containing information that can help you and the VMware Technical Support with the diagnostic and handling of support requests. For information, see Troubleshooting the Appliance.

Upgrading from Previous Releases

VMware Cloud Provider Lifecycle Manager 1.4 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

15 DEC 2022

1.4.8

20962507

  • Added support for VMware Cloud Director 10.4.1

  • Added support for VMware Chargeback 8.10 (formerly vRealize Operations Manager Tenant App)

  • Improvements in the VMware Cloud Provider Lifecycle Manager UI

Install the Interoperability Bundle

  1. From Customer Connect, download the interoperability bundle and save it locally to your machine.

  2. Login to the VMware Cloud Provider Lifecycle Manager UI by navigating to https://vcplcm-host-name, and login as vcplcm.

  3. In the top navigation bar, click Administration.

  4. Click Update Interop Bundle.

  5. In the Update interop bundle dialog, navigate to the location of the interoperability bundle and click Install Interop Bundle.

  6. After the installation process completes, refresh your browser.

Resolved Issues

Interoperability Bundle 1.4.8

  • The Network Name drop-down menu cannot display the list of networks

    When configuring a product node, if the list of networks contains a network name that is longer than 20 characters, the Network Name drop-down menu cannot display the list of networks.

Known Issues

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

  • During the VMware Cloud Director environment creation, clicking on Cancel deactivates the secondary NIC fields in the wizard

    When creating a VMware Cloud Director environment, if in the Adding new node dialog you click on Cancel and then again on Add node, the Adding new node dialog displays the secondary NIC fields as greyed out.

    Workaround:

    1. In the Adding new node dialog, click Cancel.

    2. Click on the Complete deployment setup tab and download the environment as a JSON file.

    3. Exit the deployment setup.

    4. Click Create Environment and, in the Environment Details section, upload the JSON file.

    5. Complete the environment creation process.

  • A registered RabbitMQ instance is in Incomplete status after updating the instance CPU and memory

    In VMware Cloud Provider Lifecycle Manager, if you use the Update workflow to update the CPU and memory settings for a registered RabbitMQ instance, the status of the instance changes to Incomplete.

    Workaround:

    1. In the top navigation bar of the VMware Cloud Provider Lifecycle Manager UI, click Environments.

    2. In the product card, from the Actions drop down menu, select Discover.

    3. In the Discover Product dialog box, click OK.

      If the discovery process completes successfully, the status of the RabbitMQ instance displays an OK message.

  • Adding a node and updating a certificate for a registered VMware Cloud Director instance fails with a Could not configure http and consoleproxy certificates error message

    After upgrading VMware Cloud Director, if you add a new note to the appliance or you update a appliance certificate, the operation fails with an error message.

    Could not configure http and consoleproxy certificates.

    Workaround: You must renew the VMware Cloud Director appliance certificate.

    Option 1: Renew the VMware Cloud Director certificate by using the VMware Cloud Provider Lifecycle Manager UI. For information, see Manage Product Certificates by Using the UI.

    Option 2: Renew the VMware Cloud Director certificate by logging in directly or SSH to the OS of the VMware Cloud Director appliancee. For information, see Renew the VMware Cloud Director Appliance Certificates in the VMware Cloud Director Installation, Configuration, and Upgrade Guide for the respective VMware Cloud Director version.

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

  • Updated self-signed certificate for VCP LCM UI

    During the upgrade of VCP LCM to version 1.4, a new certificate for the VCP LCM GUI is generated. The previously certificate (for 1.3) is backed up to a backup directory (/opt/vmware/cplcm/security/certs/backup ).

    The previously generated certificate was not well supported by browsers and thus the certificate is replaced in this version.

    The new certificate is also installed, if a different (non-self-signed) certificate was configured for use in VCP LCM 1.3. In that case users will have to copy back the previous certificate.

    Workaround: If the previous certificate is required to be used instead of the newly generated self signed certificate, the backup certificate should be copied back by running the following command:

    cp /opt/vmware/cplcm/security/certs/backup/vcplcm-gui.{key,pem} /opt/vmware/cplcm/security/certs/

    Once copied back, the GUI service has to be restarted to take effect:

    systemctl restart nginx.service

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

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

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