check-circle-line exclamation-circle-line close-line

vRealize Suite Lifecycle Manager 8.0.1 | 19 Dec 2019 | Build 15336196

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About vRealize Suite Lifecycle Manager 8.0.1

VMware vRealize® Suite 2019 is the complete cloud management solution, delivering and managing infrastructure and applications quickly while maintaining IT control. It provides a comprehensive management stack for IT services on vSphere and other hypervisors, physical infrastructure, and multiple public clouds. 

The vRealize Suite Lifecycle Manager automates installation, configuration, upgrade, patch, configuration management, and health from within a single pane of glass. This provides the IT Managers or Cloud admin resources to focus on business-critical initiatives, while improving time to value (TTV), reliability and consistency.

You can migrate from vRealize Suite Lifecycle Manager 1.3 version and later to vRealize Suite Lifecycle Manager 8.0.1. To know more, click here

Install VMware vRealize Suite Lifecycle Manager 8.0 or later to simplify your deployment and on-going management of the vRealize products.

What's New in vRealize Suite Lifecycle Manager 8.0.1

Note: When vRealize Suite Lifecycle Manager is upgraded from 8.0 to 8.0.1, to install vRealize Automation 8.0.1 map vRealize Automation 8.0.1 OVA to Lifecycle Manager 8.0.1. For more information, see KB article 75185.

Recommendation

  • Before you upgrade vRealize Automation 8.x to the latest version or install patch on vRealize Automation 8.x, ensure that the disk space of root partition and data partition has at least 20 GB and 48 GB of free disk space respectively. If it is HA setup, then extend the VM disk in all vRealize Automation VA nodes.
    • To increase the vRealize Automation root partition disk to meet the above requirement, increase the vRealize Automation VM Disk 1 (/dev/sda4) size to 50 GB or more WITHOUT POWERING OFF THE VA in the vCenter Server, and then run the command vracli disk-mgr resize on the vRealize Automation VA from the command shell.
    • To increase the vRealize Automation data partition disk to satisfy above requirement, increase the vRealize Automation VM Disk 2 (/dev/mapper/data_vg-data) size WITHOUT POWERING OFF THE VA in the vCenter Server, and then run the command vracli disk-mgr resize on the vRealize Automation VA from the command shell.
      Note: If the VM snapshot is present, then you cannot expand the vRealize Automation VM disk.
  • If vRealize Suite Lifecycle Manager 8.0 upgrade fails when you have provided the Repository URL, then upgrade using the CD-ROM option.

Limitations 

  • Content Migration from 1.3, 2.0 and 2.1 is not supported in vRealize Suite Lifecycle Manager 8.0.1. For more information, see Content Management
  • Support of content from an earlier version to the latest 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 Lifecycle Manager as well.
  • Multimode deployment of ISO and Template for an IaaS deployment is not supported. 
    In a single deployment of vRealize Automation, you can deploy IaaS VMs using a template or ISO. A combination of both is not supported. 
  • ISO image mapping that is specific to a locale or a user-specified operating system distribution is not supported from Lifecycle Manager
  • Scale-out of a vRealize Automation 7.x small environment is not supported in the vRealize Suite Lifecycle Manager
    To scale out vRealize Automation small HA, medium HA or a large environment, you can add the components by clicking Add Node in the product cards on the Manage Environment page.
  • 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 a snapshot 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 does not come online
    When Cassandra fails in one of the vRealize Operations nodes, this causes the vRealize Operations cluster to not come online.  

Resolved Issues

  • Users other than local VMware Identity Manager admin users cannot be used for VMware Identity Manager registration in vRealize Suite Lifecycle Manager

    When registering an external VMware Identity Manager into vRealize Suite Lifecycle Manager, the credentials of users other than local VMware Identity Manager admin users does not lead to a successful registration. This issue is resolved in this release.

  • vRealize Suite Lifecycle Manager Cloud Admin can view the Content Management tab but does not have access to the vRealize Suite Lifecycle Manager  UI 

    vRealize Suite Lifecycle Manager UI is not accessible whereas the content management tab is visible for a cloud admin. This issue is resolved in this release.

  • Content Management operations fail on vRealize Automation end-point after updating the certificate.

    The certificate can be updated on the vRealize Automation appliance through Lifecycle Manager or by using the vRealize Automation product VAMI interface. This causes content management operations to fail on vRealize Automation end-point. This issue is resolved in this release.

  • Content management functionality does not work after replacing the Lifecycle Manager certificate

    This issue occurs: 

    1. When you provide the certificate details during an OVA deployment.
    2. When you change the SSH password twice and admin password once directly from UI.
    3. The test connection fails with an invalid credential for source control endpoints only.
    4. Bitbucket, GitLab, and vSphere displays invalid credentials.

    This issue is resolved in this release.

  • vRealize Suite Lifecycle Manager does not support changed Primary Network Identifiers for vCenter Server.

    vSphere 6.5 U3 and 6.7 U3 supports updating Primary Network Identifiers (PNID) without any downtime. But vRealize Suite Lifecycle Manager 2.1 does not support this for the specified versions. 

    If PNID is changed for a vCenter server that is already registered in Lifecycle Manager with Lifecycle Manager managed products present in the vCenter server, then Lifecycle Manager loses communication with that vCenter Server. As a result, all operations on the Lifecycle Manager managed products deployed on vCenter are likely to fail.

    Workaround:

    Update 1 for PNID

    After changing the PNID:

    1. Verify if the vCenter server is still reachable from vRealize Suite Lifecycle Manager.
    2. If the vCenter Server is reachable after the PNID update, re-register the vCenter Server in vRealize Suite Lifecycle Manager.
    3. Once vCenter Server data collection succeeds then do a inventory sync and provide the correct vCenter details on retry so that Lifecycle Manager monitors the products.

    Update 2 for Scale-out of vRealize Automation

    Scale-out of a vRealize Automation 7.x small environment is not supported in the vRealize Suite Lifecycle Manager.

    • To scale out vRealize Automation small HA, medium HA or a large environment,to add the components, click Add Node in the product cards on the Manage Environment page.
    • If the small environment is installed from vRealize Automation and the load balance details are provided during the installation, scale-out of this vRealize Automation small environment is supported.

    This issue is resolved in this release.

  • Some services does not start after rebooting the vRealize Suite Lifecycle Manager appliance.

    Some services does not start even after rebooting the vRSLCM virtual appliance, as there could be some unwanted internal ports available outside after rebooting the vRealize Suite Lifecycle Manager Virtual appliance.

    After deploying the vRealize Suite Lifecycle Manager Virtual appliance from the easy installer, login to vRealize Suite Lifecycle Manager Virtual appliance through SSH and run command.

    rm -rf /etc/bootstrap/everyboot.d/10-start-services 

    This issue is resolved in this release.

  • Replacing the vRealize Automation default SSL certificate with Microsoft CA signed certificate fails due to errors in the v3 critical extensions section of the certificate.

    Microsoft CA signing process introduces v3 extensions which are not understood by vRealize Automation and certificate verification process marks the certificate as invalid. Replacing the default SSL certificate of vRealize Automation from vRealize Suite Lifecycle Manager fails with error related to "Unable to parse certificate's ['v3_extensions']['critical'] section. "

    This issue is resolved in this release.

Known Issues

  • The time settings page is not enabled to make changes when you provide NTP details after deploying vRealize Suite Lifecycle Manager​.

    On a usual scenario, when you provide the NTP details at the time of vRealize Suite Lifecycle Manager deployment, the same is reflected on the time settings page. You cannot make changes to the existing NTP details as the Select button on the UI is disabled. However, you can still select Use Host Time or Add New NTP details.  

    1. Navigate to Lifecycle Operations ->Settings -> Time Settings. 
    2. Add at-least one NTP server in vRealize Suite Lifecycle Manager UI.
      Once a new NTP server is added, the SELECT button is enabled and you can make the changes in NTP server for system.
  • vRealize Automation precheck fails while checking the VMware tools version

    vRealize Automation Precheck on SUBMIT fails while checking the guest tools version and there is no resume option on the create environment wizard to re-run the precheck.

    1. Update the VMware tool version 10.1.0 and trigger the create environment.
    2. Click Precheck.
  • vRealize Automation upgrade fails at vRealize Automation Services Restart step with an error message  

    If some of the vRealize Automation services are not started post the vRealize Automation virtual appliance upgrade within 45 minutes then the following error message appears:

    Services on this VA failed to start within 45 minutes. IaaS upgrade will not proceed. 

    Workaround:

    1. Reboot the vRealize Automation cafe VMs.
    2. Make sure all the vRealize Automation services are running.
    3. Retry the failed upgrade request from vRealize Lifecycle Manager Requests page.
  • The retry inputs provided in the failed deployment request is not saved. 

    The retry inputs provided in the failed deployment request is not getting saved and the next task in the deployment request fails again with the old input provided during the deployment.

    Workaround: Provide the retry inputs for each failed task in the deployment request or you should to re-deploy the environment with correct inputs.

  • Pre-Check succeeds but actual deployment fails due to insufficient disk space

    Pre-Check in LCM does not take extended storage into account. This means if the extended storage option is used to deploy vRealize Operation nodes using vRSLCM, then the precheck might succeed but the actual deployment can still fail due to insufficient disk space.

    Workaround: 

    To avoid deployment failure, analyze the available disk space and select appropriate data store before opting to deploy vRealize Operation from vRealize Suite Life Cycle Manager. If thin disk format is provided then user needs to make sure that sufficient disk space is available for the appliance to install. If extended storage option is opted for certain vRealize Operation nodes, then 1 TB extra storage space is required for each those nodes.

  • vRealize Automation 8.0 HA Initialize cluster fails when vRealize Automation Load Balancer configuration is wrong

    Workaround: Verfiy if the vRealize Automation Load Balancer has been configured correctly and trigger the vRealize Automation HA deployment again.

  • vRealize Automation 8.0 initialize cluster fails when SSL pass through is not enabled in NSX Load Balancer for vRealize Automation

    Workaround: Enable the SSL passthrough the vRealize Automation Load balancer before you trigger the vRealize Automation 8.0 HA deployment.

  • Adding a new node to an existing vRealize Operation cluster fails.

    Fail to initialize vRealize Operation cluster after scale-out. This issue occurs when the cluster initialization slips into indefinite waiting. This error occurs with any version of vRealize Operation.

    Workaround:

    1. Take a snapshot before attempting a scale-out. If the scale-out fails, try the Retry option from the vRealize Suite Lifecycle Manager. If the retry also fails, then delete the new VM (new node) from the vCenter server.
    2. Revert all the existing nodes to the snapshot.
    3. Return all the nodes online and then start scale out again.
  • Upgrade of vRealize Business for Cloud using Lifecycle repository always triggers an upgrade to the latest version.

    Upgrading vRealize Business for Cloud using vRealize Suite LCM Repository option from the vRealize Suite Lifecycle Manager
    always upgrades the vRealize Business for Cloud instance to the latest version independent of the selected version.

    Workaround:

    Upgrade the managed vRealize Business for Cloud instance to the required version using the Repository URL option, where the required upgrade binary is present in a repository accessible to vRealize Suite Lifecycle Manager.

  • VRCS_CUSTOM tagged workflow does not appear in the post and pre stub present under the Settings page.

    None of the existing workflows appears in the drop-down (tagged with the VRCS_CUSTOM ) post-selection of external vRO endpoint in the pre-post stub.

    Rename the existing tag of the workflow (VRCS_CUSTOM) in the vRO endpoint with "vRSLCM_CUSTOM". This displays all the workflow in the drop-down menu.

  • While migrating or upgrading content management, the source control endpoints are required to be mapped to the respective Source Control Servers again. While migrating vRealize Suite Lifecycle Manager 2.0 to 8.0.1 content library configuration in the vSphere setting page will not appear.

    Workaround:

    • Edit the required source control endpoint in the migrated or updated setup. Against the source control server, select the server from the drop-down menu which maps to this endpoint.
    • Similarly, if you are migrating from vRealize Suite Lifecycle Manager 2.0 to 8.0.1, reselect the content library from vSphere setting page within the Lifecycle Manager Environment.
  • When the vRealize Easy Installer fails at the time of deployment due to Infrastructure issues in vCenter Server, the Easy installer displays  an error message.

    Workaround: Add DNS FQDN entries of the target vCenter Server and all ESXi servers in the cluster to the system hosts file:

    For Windows:

     C:\Windows\System32\drivers\etc\hosts

    For Linux/ Mac:

      /etc/hosts 

    For more information, see Easy Installer documentation.