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

VMware vRealize Suite Lifecycle Manager 2.1 Release Notes

Updated on: 13 June 2019

vRealize Suite Lifecycle Manager 2.1 | 17 April 2019 | Build 13273278

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 2.1

VMware vRealize™ Suite 2018 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.

Install VMware vRealize Suite Lifecycle Manager 2.1 first to simplify your deployment and on-going management of the vRealize products.

What's New in vRealize Suite Lifecycle Manager 2.1

  • [New] vRealize Suite Lifecycle Manager 2.1 Patch: The patch release of vRealize Suite Lifecycle Manager 2.1 addresses some existing issues. All issues and their solutions are listed in the Knowledge Base article: KB 68067.
  • vRealize Management
    • You can now manage the lifecycle of a VMware Identity Manager provider.
  • Content Management Enhancements
    • Enable source support for an SCM endpoint like Bitbucket cloud and server.
    • Allow capturing of multiple content in one click.
    • Support for newer vRealize Automation content types  
  • Improve VMware Validated Design with Lifecycle Manager
    • VVD specifications as a marketplace content now describe that the environment configuration is consumable from Lifecycle Manager.
  • Certificates Management
    • With Lifecycle Manager 2.1, you can now add and support Product component level certificates. 
  • Other Improvements: 
    • You can now delete a single product from an environment.
    • Ability to deploy products to a specific folder.
    • Support for NTP server configuration for the LCM appliance. 
    • Embedded vRealize Orchestrator and vRealize Cloud Client are removed.
    • UI\UX improvement: Settings view and user flow enhancements.

Limitations 

  • Support of content from an earlier version to the latest depends on the product capabilities.  
  • 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
  • vRO package name cannot contain special characters and the package is not validated
    A vRO package name cannot contain special characters and can cause issues when you capture, release or check-in a content. If you have a vRO package name with a space in between the name, then the space is converted to an underscore (_) during a capture and fails during a test and deploy.
  • If the environment name contains a space then GET drift report which uses API does not appear
    If the environment name contains a space then GET drift report which uses API does not appear.
  • Scale-out of a vRealize Automation 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.
  • Day 2 operations fail after you deploy or import an environment by using vRealize Suite Lifecycle Manager
    After deploying the vRealize suite of products by using vRealize Suite Lifecycle Manager, if any of the VMs are migrated across a vCenter, such product VMs will not be managed by vRealize Suite Lifecycle Manager.  
  • Delete environment or snapshot fails when vCenter credentials are changed after the environment is deployed
    When you change vCenter credentials after an environment is imported or deployed successfully in the vRealize Suite Lifecycle Manager, delete environment operations and snapshots in the environment fail.
  • Inconsistent pre-stub and post-stub test execution in the content pipeline with multiple endpoints
    When multiple endpoints are involved in a test or release, the deploy workflow runs pre-stubs once per endpoint and post-stub once for the complete job.
  • vRealize Orchestrator package can scale up to 1000 elements in a package.
    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.
  • Test and deployment of a content is getting failed in an Azure machine
    vRealize Suite Lifecycle Manager does not support an Azure machine in content management for testing and releasing content. 
  • You can see multiple catalog app tiles and application links of vRealize Suite Lifecycle Manager after you register with VMware Identity Manager
    After you register with VMware Identity Manager in vRealize Suite Lifecycle Manager, and you click Update from the Settings > User Management tab multiple times, an equal number of catalog application tiles and application links of vRealize Suite Lifecycle Manager are created.
  • 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.  
  • Test and deployment of XaaS blueprint "Azure Machine" shipped by default with vRealize Automation fails
    XaaS blueprint "Azure Machine" is shipped by default with vRealize Automation. However, transfer of XaaS blueprint between vRealize Automation environments is not supported.

vRealize Suite Lifecycle Manager 2.1 Product Support Pack 2 for vRealize Network Insight 4.1.1

Announcing the general availability of vRealize Suite Lifecycle Manager Product Support Pack. 

Note: This is an accumulative support pack that supports both 4.1.0 and 4.1.1 versions of vRealize Network Insight.  

The earlier versions of VMware Identity Manager 3.2.0 are not integrated with vRealize Network Insight version 4.1.0 and 4.1.1.

Update the vRealize Network Insight version when vRealize Lifecycle Manager is connected to the internet:     

  1. Access Lifecycle Manager UI and navigate to Home > Settings > Update.
  2. Scroll down to Support for Additional Product Versions section. The vRealize Suite Lifecycle Manager auto-populates the list of available support versions. If the list is not auto-populated, click Check for Versions.
  3. When the list is populated, click Apply Version for the appropriate content version.
  4. The Support for Additional Product Versions section displays the updated version of the policy and includes vRealize Network Insight 4.1.1 under the Product Versions Info.

Note: Alternatively, you can navigate to the context menu after you have logged in. Click Products to search for vRealize Network Insight 4.1.1.

Update the vRealize Network Insight version when vRealize Lifecycle Manager is not connected to the internet:     

  1. Download the product support pack file from the VMware Market place.
  2. From the vRealize Lifecycle Manager UI, navigate to Home > Settings > Update.
  3. Scroll down to Support for Additional Product Versions section.
  4. To upload the downloaded product support pack file, click Choose File. The vRealize Suite Lifecycle Manager auto-populates the list of available support versions.
  5. When the list is populated, click Apply Version for the appropriate content version.
  6. The Support for Additional Product Versions section displays the updated version of the policy and includes vRealize Network Insight 4.1.1 under the Product Versions Info.

Note: Alternatively, you can navigate to the context menu available after you have logged in.  Click Products to search for vRealize Network Insight  4.1.1.

After you have added the .pspak file successfully, refresh the UI.

Click here to download the product support pack. 

Resolved Issues

  • [New] Deployment of vRealize Network Insight with vRealize Identity Manager fails while creating vRealize Identity Manager user

    Even if a user exists in vIDM, the vRealize Network Insight deployment with vRealize Identity Manager fails with the following error:

     Error occurred while creating vIDM user of vRNI. Not Found 

    When you retry, you are requested to provide the following credentials: 

    • Vidmusername
    • ​Vidmdisplayname
    • Vidmdomain

    This issue is resolved in this release.

  • You cannot enter the details for a User DN if Lifecycle Manager is upgraded from 1.0 or 1.1 with pre-integrated VMware Identity Manager

    This issue occurs because the User DN field is introduced only from Lifecycle Manager version 1.2. This field was not present in earlier versions of Lifecycle Manager and therefore, you cannot edit the AD details in Lifecycle Manager after attaching a VMware Identity Manager. For more information, see KB article 56336. This issue is resolved in this release.

  • If the HA protect mode is enabled for a VM, VM installation using Lifecycle Manager fails.

    When you are trying to deploy a VM through Lifecycle Manager, if the VM has HA protection enabled, the deployment fails with the following error: 

    ERROR: EngineException: Unknown Error Happened During Deployment

    This error is encountered when you are try to deploy vRealize Automation.

    This issue is resolved in this release.

  • The deployment of vRealize Network Insight using Lifecycle Manager fails with an exception. 

    When you deploy VMware Network Insight using Lifecycle Manager, VMware Network Insight deployment fails with the following exception: 

    Problem while creating Import Params: Duplicate element 'InstanceID'

    This issue is observed when you deploy VMware Network Insight on vCenter 6.7 U1 or later versions with Lifecycle Manager. For more information, see KB article 67103. This issue is resolved in this release.

  • The deployment of vRealize Log Insight using Lifecycle Manager fails with an exception. 

    When you deploy vRealize Log Insight using Lifecycle Manager, the deployment fails with the following exception: 

    com.vmware.vrealize.lcm.common.exception.vcenter.ImportSpecCreationException: 
    Problem while creating Import Params: Duplicate element ‘InstanceID’

    This issue is observed when you deploy vRealize Log Insight on vCenter 6.7 U1 or later version with Lifecycle Manager. For more information, see KB article 67103. This issue is resolved in this release.

  •  Deployment of products fail when a JSON config file contains certificate.

    The exported JSON spec from a Lifecycle Manager environment contains a certificate at the node level. When this JSON is used for deployment in another Lifecycle Manager environment, then the certificate is overridden by the certificate provided at the infra level. The deployment fails if the certificates are different. This issue is fixed in the Lifecycle Manager 2.0 patch. For more information, see KB article 59658.

    This issue is resolved in this release.

Known Issues

  • [New]: 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 Settings -> System Administration -> 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 will get enabled and user can make the changes in NTP server for system using SELECT button.
  • [New] 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.

    Workaround

    Open SSH in Lifecycle Manager, and run the following command:

    systemctl restart blackstone-spring
  • The / Characters cannot be used in the name for Topology or Text ResourceKind Metrics  

    The / Characters cannot be used in the name for Topology or Text ResourceKind Metrics as the export fails.

  • vRealize Business for Cloud upgrade may fail if the root passwords of vRealize Business for Cloud server and vRealize Business for Cloud Remote Collector are not same

    When you upgrade vRealize Business for Cloud using Lifecycle Manager UI, the server and the remote collector should have same root passwords. If the passwords are different then upgrade may fail and you are asked to enter the correct password in the retry.

  • Deployment of a vRealize Operations Symptom fails with an error message

    When a symptom definition is setup with REGEX or NOT_REGEX, the import fails using the vRealize Operation APIs with the following error. 

    Error releasing Operations-Symptom message= "Invalid request... #1 violations found.","validationFailures":[{"failureMessage":"Message Event Condition field 'operator' must be either EQ or CONTAINS

    Workaround: If a symptom uses REGEX, the content needs to be imported manually through Lifecycle Manager UI. 

  • 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.
  • Some content may not release between different versions of vRealize Operations

    Content release from different versions of vRealize Operations may fail. For example, content from 6.6 to 6.7 some content types may fail.

  • For a given ISO image, if Windows ISO has a name that is already present in the content library LCM-LOCAL-ISO-LIB, then Lifecycle Manager ignores Windows ISO upload  

    When LCM uploads the ISO deployment to a vCenter content library named – LCM-LOCAL-ISO-LIB, after an ISO is mapped in Lifecycle Manager, note the entry under the column ISO Binary in the ISO Binaries table. If Lifecycle Manager uploads ISO binary by the same name in the vCenter content library mentioned earlier then such uploads are ignored. 

    Workaround:

    Manually delete the ISO file from content library LCM-LOCAL-ISO-LIB.

  • 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 Manageror by using the vRealize Automation product VAMI interface. This causes content management operations to fail on vRealize Automation end-point.

    Workaround:

    Once a certificate is replaced by Lifecycle Manager, a restart of the embedded vRealize Orchestrator is required on the LCM appliance for the Test Connection and all other content operations to continue to work. Note that this is required for vRealize Automation endpoint only. 

    SSH to the LCM Appliance as user root and run the command:

    "systemctl restart vco-server"

  • Data is not loaded into vRealize Suite Lifecycle Manager UI after upgrading from vRealize Lifecycle Manager 1.2 to 1.3

    After upgrading from vRealize Suite Lifecycle Manager from 1.2 to 1.3, older data not available in LCM. You cannot see older data in LCM such as older Datacenters, Environments, vCenter Servers, and Requests. The newer requests are successfully created and visible in the UI.

    Workaround:

    See KB article 56782

  • After a successful Lifecycle Manager upgrade, the updated version is not visible in the 'About' section and under the Settings page at times

    After a successful upgrade of Lifecycle Manager, the reflecting appliance version might still reflect an older version. This issue occurs when the Lifecycle Manager reboot happens prematurely before the upgrade is completed.

     Workaround: Click Reboot from the Update tab under the Lifecycle Manager Settings tab.

  • Accessing vRealize Suite Lifecycle Manager from IE-11 show glitches in UI

    You can see some glitches in the UI when accessing vRealize Suite Lifecycle Manager.

    Workaround: Use other supported browsers like Chrome or Mozzila FireFox.

  • Prolonged activity for 15 to 30 minutes only on the content pipelines page leads to session timeout for Lifecycle Manager.

    Working continuously on Content pipelines page without clicking other tabs of Lifecycle Manager leads to Session Timeout.

    Workaround: Clicking the other tabs or pages of Lifecycle Manager intermittently will not cause this issue. 

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

     Workaround: Use local VMware Identity Manager admin user credentials for registration of VMware Identity Manager to vRealize Suite Lifecycle Manager.

  • After a successful remediation, the report in the drift report page does not change

    After a successful remediation on any drifted configuration parameter is performed, the report will not reflect the changes immediately in the drift report page. The report is in red state. 

    Note: The remediated parameter(s) will still report as drifted even after a successful drift report run in case the remediated value is different from the current baseline value. In that case, you can choose to save a new baseline by clicking on the "Save Baseline" in the remediation requests page.

    Workaround:  Wait until the next drift report is successfully executed and check the interval in System setting page with the text "Configuration Drift Interval".

  • When a Lifecycle Manager upgrade is triggered, the screen stays at Maintenance mode and Home page never comes up.

    After an upgrade, there can be some errors in the content from the marketplace. The content might contain a few request that prevents the service to start. Lifecycle Manager UI displays a maintenance mode message and the Home page is not displayed.  

    Workaround:

    Restart the xenon server. If the issue still persists, delete the error request and restart xenon.

  • Remediation does not modify the property Configure ESXi Hosts in vRealize Log Insight vSphere integration

    When you trigger remediation in vRealize Suite Lifecycle Manager, the process does not modify the vRealize Log Insight vSphere integration property Configure ESXi Hosts.

    Workaround: Modify the property Configure ESXi Hosts in vRealize Suite Lifecycle Manager vSphere integration endpoint configuration.

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

    Workaround: Add a new role as a developer or a release manager.

  • 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.
  • In Lifecycle Manager 1.2 or earlier versions, vrlcm-xserver.log/console.log displays an error message 

    Due to incorrect content in Marketplace server, scheduled or on-demand market place sync request status remains in "IN PROGRESS" state and vrlcm-xserver.log, vrlcm-server.log displays the following error messages:  

    "Failure serializing state of service /lcm/api/request/**********"

    Workaround: Cleanup requests with DELETE "/lcm/api/request/**********" API and upgrade to the latest version of Lifecycle Manager. 

  • Installation of Content fails on a newly created environment

    The license of newly created environments cannot be listed until a marketplace sync is triggered.

    Workaround: Sync Marketplace from the UI.
     

  • Request to capture and deploy Windows Customization spec that contains a password fails

    When transferring a customization spec between vCenter servers the password fields cannot be decrypted by the target. This causes deployments that depend on custom specs with passwords to fail.

    Workaround: Manually enter the correct value in the Administrator password field after customization spec is deployed by the Lifecycle Manager pipeline.