Release Details

Here is the release date and build number for vRealize Suite Lifecycle Manager 8.10 release.

For information about product support packs for vRealize Suite Lifecycle Manager 8.10, see VMware vRealize Suite Lifecycle Manager 8.10.x Product Support Pack Release Notes.

For information about Patch 1 for vRealize Suite Lifecycle Manager 8.10, see VMware vRealize Suite Lifecycle Manager 8.10 Patch 1 Release Notes.

Release

Release Date

Build Number

VMware vRealize Suite Lifecycle Manager 8.10.0

11 October 2022

20594451

What's New

Here are the key features and capabilities of vRealize Suite Lifecycle Manager 8.10:

  • VMware Cloud Foundation Enhancements

  • vRealize Suite Lifecycle Manager now provides integration between vRealize Suite products. With vRealize Log Insight, you can now perform log forwarding configuration from other vRealize Suite products to vRealize Log Insight. Similarly, with vRealize Operations Manager, you can now perform management pack configuration of other vRealize products in vRealize Operations Manager.

  • Usability Enhancements

  • You can enable or disable health checks for vRealize Suite products in vRealize Suite Lifecycle Manager.

  • vRealize Automation Enhancements

  • - If vRealize Automation upgrade fails, an auto-revert feature is introduced to revert back the appliance to its previous working state. Before auto-revert, a support bundle from vRealize Automation is automatically collected and stored in vRealize Suite Lifecycle Manager for troubleshooting purpose. You can go to the affected vRealize Automation product in vRealize Suite Lifecycle Manager and download the latest-generated support bundle.
  • - Participation in the Customer Experience Improvement Program for vRealize Automation is now available using the Pendo Customer Experience Program (Pendo CEIP).

  • PSPR Enhancements

  • If you have five failed login attempts in vRealize Suite Lifecycle Manager, your account will be locked with an error message.

  • vRealize Operations Manager Enhancements

  • Remote collectors are now renamed as Cloud Proxy nodes in vRealize Operations Manager version 8.10.

Recommendations

  • VMware Cloud Foundation users must upgrade to version 4.5 to be supported on vRealize Suite Lifecycle Manager 8.10.0 and vRealize Suite products version 8.10.0.

  • If the source vRealize Automation has 8.0.0 GA or 8.0.1 GA, ensure that KB 78235 is applied before upgrading to restore expired root accounts.

  • When configuring multi-tenancy in vRealize Suite Lifecycle Manager for VMware Identity Manager and vRealize Automation, if you replace VMware Identity Manager certificate, it can cause service downtime on products integrated with VMware Identity Manager. Hence, it is suggested to create SAN certificates with required hostnames for multi-tenancy. To avoid service disruption, use wildcard certificates on VMware Identity Manager.

  • To reboot VMware Identity Manager cluster setup, use the Power On and Power Off options in the VMware Identity Manager product actions in vRealize Suite Lifecycle Manager.

Limitations

  • vRealize Suite Lifecycle Manager cannot be upgraded using VMware Remote console in Windows VM: During an vRealize Suite Lifecycle Manager upgrade, the ISO filename is truncated after it is mounted in Windows VM. For an upgrade, ensure that you upload the ISO filename in a content library of the vCenter server or upload it to a datastore that the vRealize Suite Lifecycle Manager VM can access. After uploading the ISO filename, attach the ISO to the CD-ROM device of the vRealize Suite Lifecycle Manager VM by editing the hardware configuration from the vCenter inventory of the VM. From the vRealize Suite Lifecycle Manager UI, select CD-ROM based upgrade option, and then click proceed.

  • If a custom form is released without a blueprint at the target vRealize Automation, even if the release is successful on vRealize Suite Lifecycle Manager, the custom form is not visible at the target vRealize Automation instance. To release a custom form, ensure that the asociated composite blueprint is released or created first on the target vRealize Automation.

  • Content source on vRealize Automation 8.x endpoint: When releasing a blueprint on vRealize Automation 8.x, you must create the content source on the target vRealize Automation 8.x prior to the release.

  • vRealize Automation 8.x content types: The vRealize Automation 8.x content types which are renamed must be re-captured from the vRealize Automation endpoints, and then checked in to the source control endpoints. If the content is present in the source control, then you must manually rename the folder in the source control endpoints, and then check-out the content from the source control endpoints.

  • Content Migration from 1.3, 2.0 and 2.1 are not supported in vRealize Suite Lifecycle Manager 8.0.1 and later. For more information, see Content Management.

  • Support of content from an earlier version to the latest version depends on the product capabilities: You can capture content from vRealize Automation 7.5 and release to vRealize Automation 7.6. However, if vRealize Automation 7.6 does not support contents captured from older version, it would not work in vRealize Suite Lifecycle Manager.

  • vRealize Orchestrator package can scale up to 1000 elements in a package.

  • Snapshot for VMs remain in the in-progress state in vRealize Suite Lifecycle Manager: Snapshot for VMs that have device back up are not supported and remain in the in-progress state in vRealize Suite Lifecycle Manager. You cannot take snapshots of VMs that have a device back up in vCenter. vRealize Suite Lifecycle Manager also supports taking snapshots of VMs. However, the vCenter server also supports taking device back up. For such VMs, vRealize Suite Lifecycle Manager snapshot requests would remain in progress.

  • vRealize Operations upgrade failed at application upgrade task after completing the OS upgrade task and the cluster is not online: When Cassandra fails in one of the vRealize Operations nodes, this causes the vRealize Operations cluster to be offline.

  • vRealize Suite Lifecycle Manager 8.10 is not compatible with earlier versions of VMware Cloud Foundation such as 4.4 and 4.4.1. vRealize Suite Lifecycle Manager 8.10 is compatible with VMware Cloud Foundation version 4.5.

Resolved Issues

  • vCenter data collection request fails after vCenter password rotation from SDDC manager

    In the SDDC manager when starting the vCenter service account password rotation, the password is reset but the vRealize Suite Lifecycle Manager inventory password update request fails. This issue is observed when the vRealize Suite Lifecycle Manager contains a vRealize Network Insight environment that is managed with data sources.

    This issue was reported in vRealize Suite Lifecycle Manager 8.8 and is resolved in vRealize Suite Lifecycle Manager 8.10.

  • The upgrade flow from vRealize Suite Lifecycle Manager is optimized

    When upgrading a product from vRealize Suite Lifecycle Manager, issues with reading the vCenter details can hinder the upgrade flow. This issue is now resolved through optimization of the upgrade flow.

Known Issues

  • Do not use VMware Repository option when upgrading Orchestrator.

    The vRealize Orchestrator application cannot be upgraded to VMware Aria Automation Orchestrator 8.12.x by using the VMware Repository option. This option is intended for internal test and is not functional for external users.

    Workaround:

    When upgrading the vRealize Orchestrator application to VMware Aria Automation Orchestrator 8.12.x in the Environments section of the Lifecycle Operations service of VMware Aria Suite Lifecycle, select either VMware Aria Suite Lifecycle Repository or Repository URL as the Repository Type option. Do not select the VMware Repository option.

  • The APUAT report is not updated for vRealize Operations Manager 8.10.2 within the lcmcontents directory when using vRealize Suite Lifecycle Manager 8.10 PSPack 7

    When running a APUAT assessment when starting a product upgrade from vRealize Operations Manager 8.10.0 or 8.10.1 to vRealize Operations Manager 8.10.2, the generated assessment report is blank.

    Workaround: You can continue with the upgrade but the generated assessment report is blank. This known issue is expected to be resolved in a future release of vRealize Suite Lifecycle Manager.

  • The upgrade availability message is displayed incorrectly in the latest version of vRealize Suite Lifecycle Manager

    Under the System Upgrade page, you can check for upgrade availability by clicking Check for Upgrade. If there is no newer version, you should receive a No Upgrade Available message. However, after upgrading your vRealize Suite Lifecycle Manager environment to the latest version, checking for upgrade availability displays a blank red banner.

    No workaround.

  • Content Management is not supported for vRealize Operations Manager version 8.10.0

    Content Management in vRealize Suite Lifecycle Manager version 8.10.0 does not support vRealize Operations Manager version 8.10.0. Realize Suite Lifecycle Manager version 8.10.0 supports vRealize Operations Manager version 8.6.4 and earlier 8.x versions of vRealize Operations Manager.

    No workaround. Content Management support for vRealize Operations Manager version 8.10.0 will be available in the future releases.

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