Updated on: 28 Feb 2019 vRealize Suite Lifecycle Manager 2.0 | 20 September 2018 | Build 10150522 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.0
• What's New in vRealize Suite Lifecycle Manager 2.0
• Resolved Issues
• Known Issues

About vRealize Suite Lifecycle Manager 2.0

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.0 first to simplify your deployment and on-going management of the vRealize products.

What's New in vRealize Suite Lifecycle Manager 2.0

• vRealize Suite Lifecycle Manager 2.0 Patch: The patch release of vRealize Suite Lifecycle Manager 2.0 also addresses some existing issues and support for vRealize Network Insight 4.0. All issues and their solutions are listed in the Knowledge Base article: KB 65098.
• Certificate Management

  • You can manage certificates used across vRealize product environments from a single place.

  • You can replace product certificates as Day-2 operation

  • Ability to specify certificates at both product and environment level

• Support for Patching

  • Seamless mechanism to automatically discover and apply product patches.

  • You can view and download the audit history of patches applied at both product and environment level.

• Content Management Enhancements

  • Support for vRealize Operations content - Support a first-class content with a dependency discovery for Dashboards, Reports, View, Alerts, Symptoms, Recommendations, Text, Topology, and Resource Metrics. 

  • Support for deploying multiple contents - Ability to deploy multiple contents to respective endpoints in a single operation

  • Rich content filtering - Ability to filter content based on associated metadata such as tag, endpoint(s), content type, save and reuse filters.

  • Content Developer restricted to a read-only view of endpoints created by others. Release Manager roles will continue to have access over all endpoints. 

•  Other Improvements: 

  • Simpler process to onboard and subsequently manage existing product environments.

  • Support for deploying Windows machines from ISO or VM Templates as part of creating vRealize Automation instance.

  • Ability to import vCenter Servers in bulk. 

  • Ability to import and update passwords in bulk on vRealize Network Insight data sources. 

  • Notifications 

  • Ability to filter and export user requests. 

Limitations 

• 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 vRealize Suite 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.
• vRLSCM upgrade from 1.2 to 1.3 will not upgrade if the execute permission is not available for /etc/vlcm/upgrade-va
  vRLSCM upgrade from 1.2 to 1.3 will not upgrade if the execute permission is not there for /etc/vlcm/upgrade-va. See KB Article 56511.
• 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 Life Cycle 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.
• vRO package can scale up to 1000 elements in a package.
  vRO 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 Life Cycle 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.0 Product Support Pack

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

This product support pack is over vRealize Suite Lifecycle Manager 2.0 and adds support for the following products:

1. vRealize Automation 7.3.1
2. vRealize Log Insight 4.6.2 and 4.7.1 

For more information, see KB 60237.

Click here to download the product support pack. 

Resolved Issues

• [New] The deployment of vRealize Network Insight using vRealize Suite Lifecycle Manager fails with an exception. 

  When you deploy vRNI using vRealize Suite Lifecycle Manager, vRNI deployment fails with the following exception: 

  Problem while creating Import Params: Duplicate element 'InstanceID'

  This issue is observed when you deploy vRNI on vCenter 6.7 U1 or later versions with vRealize Suite Lifecycle Manager. For more information, see KB article 67103.

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

  When you deploy vRealize Log Insight using vRealize Suite 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 vRLI on vCenter 6.7 U1 or later version with vRealize Suite Lifecycle Manager. For more information, see KB article 67103.

• If an admin role is not present for the given vCenter user in a vCenter Server 6.7, install precheck fails with an error   

  Install precheck and product deployment fails, if the vCenter Server 6.7 user has the privileges assigned as per vRealize Suite Lifecycle Manager documentation. This issue is fixed in the vRealize Suite Lifecycle Manager 2.0 patch. For more information, see KB article 59658. vCenter Server 6.7 and 6.7 U2 are supported in Lifecycle Manager 2.0 Patch 1 and higher.

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

  The exported JSON spec from a vRealize Suite Lifecycle Manager environment contains a certificate at the node level. When this JSON is used for deployment in another vRealize Suite 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 vRealize Suite Lifecycle Manager 2.0 patch. For more information, see KB article 59658.

• [New] Upgrade to vRealize Network Insight  3.9.0 fails

  Apply the pre-upgrade patch before you upgrade to vRealize Network Insight 3.9 from 3.7 or 3.8 versions. For more information, see https://kb.vmware.com/s/article/59443. This issue is fixed in the vRealize Suite Lifecycle Manager 2.0 patch. For more information, see KB article 59658.

  Apply pre-upgrade patch bundle file "vRealizeNetworkInsight-pre-upgrade-fix.bundle" before upgrading to vRealize Network Insight 3.9.0. Click here for the patch.

• Add Products and Scale Out actions fail when you configure the certificate for a product  

  When you use the Add Products or Scale Out actions to modify an environment, the product can fail if the new product host names or the components are not present in the SAN certificate. 

• vRealize Automation installation of a database task fails even when a database is already present 

  vRealize Automation installation of a database task fails even though you have provided the database user name and password with a useExistingdb flag set as true and useWindowsAuthentication flag set as false in the config file.

• When you try to download a support bundle for vRealize Network Insight 3.8.0, vRealize Suite Lifecycle Manager request will be completed but the support bundle is not downloaded.

  For vRealize Network Insight 3.8.0, if you try to download the support bundle using vRealize Suite Lifecycle Manager, vRealize Suite Lifecycle Manager request will initiate the support bundle generation on all the available nodes. Once vRealize Suite Lifecycle Manager request is completed, support bundle will get generated in the vRNI environment. But they will not be downloaded in vRealize Suite Lifecycle Manager environment. 

• When you change Admin Password of a vRealize Automation HA appliance, the existing password of a secondary node does not change.

  When you change the Admin password for a vRealize Automation HA appliance by navigating to Home>Environment, this will not change the password on the secondary cafe node. This might break the vRealize Automation Cafe cluster.

• vRealize Suite Lifecycle Manager upgrade fails if the root file system has less than 3 GB of space​

  After you trigger an upgrade, the version in the vRealize Suite Lifecycle Manager update page shows upgrade completed successfully after some time but the appliance version still displays an older version. The  /opt/vmware/var/log/vami/updatecli.log file contains an error with an exit code 10752. 

• Content name with a space displays an error

  If a content name contains a space, you cannot check-in that content into the source control server.

• When multiple vIDM roles and users are configured, upgrade to vRealize Suite Lifecycle Manager 1.3 causes loss of user and role information[

  vIDM login for previously configured users stops working. The previously configured user roles in vRLCM 1.2 are not displayed under Settings - User Management - Access Control tab. You can add previously configured roles again.

• After you replace the certificate in vRealize Suite Lifecycle Manager appliance on reboot the old certificate is displayed in the browser.

  After you replace the certificate in vRealize Suite Lifecycle Manager appliance, on reboot old certificate getting applied to the vRealize Suite Lifecycle Manager instance.

• Import of an existing vRealize Network Insight environment into vRealize Suite Lifecycle Manager does not import data sources that are present in vRealize Network Insight 

  Import of an existing vRealize Network Insight environment succeeds in vRealize Suite Lifecycle Manager but the data sources cannot be imported and cannot be present in the Manage environment page product component list.

• Content management does not capture fields that are marked as secured while capturing vRealize Automation Content. 

  If the content has a secure field, like a password that is not present in the plain text, content management does not capture those fields. 

Known Issues

• [NEW] If HA protect mode is enabled for a VM, VM installation using vRealize Suite Lifecycle Manager fails.

  When you are trying to deploy a VM through vRealize Suite 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 seen when trying to deploy vRealize Automation.

  Disable the HA protect mode at the vSphere cluster level and proceed with the deployment.  

• 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 vRealize Suite 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 vROPS 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 vRealize Suite Lifecycle Manager UI. 

• vRealize Automation precheck fails while checking the VMware tools version

  vRA 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 vRealize Suite 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 vRealize Suite Lifecycle Manager, note the entry under the column ISO Binary in the ISO Binaries table. If vRealize Suite 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 vRealize Suite Lifecycle Manager or 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 vRealize Suite 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 vRA 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 vRCLM 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 vRealize Suite 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 vRealize Suite Lifecycle Manager, the reflecting appliance version might still reflect an older version. This issue occurs when the vRealize Suite Lifecycle Manager reboot happens prematurely before the upgrade is completed.

  Workaround: Click Reboot from the Update tab under vRealize Suite 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 around 15 to 30 minutes only on the content pipelines page leads to session timeout for vRealize Suite Lifecycle Manager.

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

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

• Users other than local vIDM admin users can not be used for vIDM registration in vRealize Suite Lifecycle Manager

  When registering an external vIDM into vRealize Suite Lifecycle Manager, the credentials of users other than local vIDM admin users does not lead to a successful registration.

  Workaround: Use local vIDM admin user credentials for registration of vIDM 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 vRealize Suite 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 few request that prevents the service to start.  vRealize Suite 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 Life Cycle Manager Cloud Admin can view the Content Management tab but does not have access to the vRealize Suite Life Cycle Manager  UI 

  vRealize Suite Life Cycle Manager UI is not accessible whereas the content management tab is visible for a cloud admim.  

  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 vRA 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 vRLCM Requests page.
• In vRealize Suite 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 vRealize Suite Lifecycle Manager 1.3.

• You cannot enter details for User DN if LCM 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 LCM version 1.2. This field was not present in earlier versions of LCM and hence you cannot edit the AD details in LCM after attaching a vIDM. For more information, see KB article 56336.

• 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 vRealize Suite Lifecycle Manager pipeline.