What's in the Release Notes

These release notes cover the following topics:

About vRealize Suite Lifecycle Manager 1.0
What's New in vRealize Suite Lifecycle Manager 1.0
Known Issues

About vRealize Suite Lifecycle Manager 1.0

VMware vRealize™ Suite 2017 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 1.0 first to simplify your deployment and on-going management of the vRealize products.

What's New in vRealize Suite Lifecycle Manager 1.0

vRealize Suite Lifecycle Manager automates Day 0 to Day 2 operations of the entire vRealize Suite, enabling simplified operational experience for customers. vRealize Suite Lifecycle Manager automates lifecycle management with a single pane of glass, thereby freeing customer resources to focus on business-critical initiatives, while improving time to value (TTV), reliability, and consistency. Key capabilities include:
- Simplified new install of vRealize Suite Lifecycle Manager
  - Product & solution -based install
  - Standardized deployment sizing (S/M/L)
  - Silent install (infrastructure as code)
- Brownfield environment support for importing existing environment
- Single sign-on (vIDM integration)
- GUI & API based
- Export configuration (JSON template)
- Snapshot and one-click upgrade
- Day 2 Operations - scale-out, organic growth
- Pre-checks & validation
- myvmware.com integration
- Configuration management and drift reporting
- Health monitoring through integration with vROPS SDDC Health
- Error handling / log bundles
- Aligned with VMware reference architecture & validated designs
Backup and restore with EMC Avamar.

For information about what’s new in the vRealize Suite 2017 products, see the release notes for the individual products.

Known Issues

For known issues with vRealize Suite 2017 products, see the release notes for the individual products.

The following issues are known to occur in vRealize Suite Lifecycle Manager.

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.
vRealize Operations Manager UI access from vIDM app catalog displays a 404 error
When you access vRealize Operations Manager from vIDM vApp Catalog for the second time after closing the vRealize Operations Manager tab opened for the first time, then vRealize Operations Manager UI displays a 404 error.

Workaround:Clear your browser cache and try again.
vRealize Business remote collector component is not listed in the vRealize Business product details page
When the vRealzie Business server that has vRealize Business remote collector components imported to vRealize Suite Lifecycle Manager, the vRealize Business remote collector components are not listed on the vRealize Business product details page.

Workaround: None.
Use of systemctl or service commands for start/stop/restart/status of service daemons might not work as expected
Server daemon processes vlcm-server and vlcm-xserver do not integrate property with systemd and may behave unexpectedly when used with systemctl or service commands. For example, systemctl restart vlcm-server.

Workaround: Use /etc/init.d/vlcm-server(or vlcm-xserver) {start,stop,restart} to interact with these daemon processes.
vRealize Suite Lifecycle Manager does not work on Microsoft Internet Explorer 11
vRealize Suite Lifecycle Manager does not support Microsoft Internet Explorer 11 in this release.

Workaround: Choose a different browser to access vRealize Suite Lifecycle Manager.
When you add a replica node to an existing vRealize Operations Manager environment, the replica node does not join the vRealize Operations Manager cluster and the node addition/scale-out operation fails in vRealize Suite Lifecycle Manager
When you do a scale out/component addition to an existing vRealize Operations Manager, replica node addition fails. The replica VM is deployed, but when it tries to join the vRealize Operations Manager cluster, it fails. Consider a situation where the vRealize Operations Manager setup has a master node. You can add three types of nodes at this time: data node, replica node, and remote collector. Adding a data node or remote collector works fine, but adding a replica node fails.

Workaround: Use the vRealize Operations Manager user interface to add the replica node.
Product component details such as CPU, memory, power status, and version do not display under the product details page in Manage Private Cloud
When the suite product components are spread across two vCenters, and if you have not specified both vCenters as part of the import brownfield for the product, then component details that belong to the vCenter that is not provided aren't visible in the product details page.

Workaround: Provide both vCenters at product level during the import brownfield environment process even though one of the vCenters is provided in infrastructure level inputs.
Business Management tab not visible in vRealize Automation UI after suite deployment.
If VMware Identity Manager is registered with vRealize Suite Lifecycle Manager, vRealize Business for Cloud might not have registered to vRealize Automation after successful deployement of the suite, causing the Business Management tab to not appear in the vRealize Automation UI.

Workaround: During vRealize Suite deployment, specify masterVidmEnabled property set to False in vRealize Buisness for Cloud server component in advanced properties of the suite install wizard.
vRealize Log Insight self-signed SSL certificate is not replaced by a vRealize Suite Lifecycle Manager custom certificate
By default, vRealize Log Insight installs a self-signed SSL certificate on the virtual appliance. vRealize Suite Lifecycle Manager generates custom certificates for products during environment creation, but custom certificate generation fails for vRealize Log Insight. The default vRealize Log Insight self-signed certificate generates security warnings when you connect to the vRealize Log Insight web user interface. If you enabled Integrated Load Balancer, you must generate a new certificate using the ILB IP as common name and replace the certificatesor the vRealize Log Insight Agents configured to connect to the Log Insight server through SSL rejects the connection.

Workaround: Generate or get a custome CA signed certificate. The generated certificate can be a wildcard, SAN, or ILB IP certificate.
Upload the generated certificate to vRealize Log Insight from the SSL configuration menu on the Administration tab.
VMware Identity Manager authentication to vRealize Automation fails
Authentication to vRealize Automation via external VMware Identity Manager, either by clicking on the vRealize Automation application icon in the VMware Identity Manager catalog or manually logging in to vRealize Automation via the tenant URL, fails with the following error:Identity Manager encountered an error. Contact your admin and provide information displayed below.

Ask your administrator to check the time on the VMware Identiy Manager and vRealize Automation virtual appliance to verify that they are properly synchronized.
When the baseline configuration is created for vRealize Business for Cloud, Azure endpoints that have been configured are not collected and analyzed for configuration changes
In cases where you add an Azure public cloud endpoint the vRealize Business for Cloud after you have created a product baseline for that instance of vRealize Business for Cloud in vRealize Suite Lifecycle Manager, configuration drift reports in vRealize Suite Lifecycle Manager do not capture configurations for the Azure endpoint.

Workaround: None.
Configuration drift fails when vRealize Automation primary and secondary virtual appliance nodes have different root passwords or the vRealize Operations Manager master node has a different root password than other nodes
When an existing vRealize Suite is imported into vRealize Suite Lifecycle Manager and the primary and secondary virtual appliance root passwords differ, virtual machine-related configurations like certificates, network details, and file based configurations are not collected from all virtual appliances as part of the baseline creation. Only the master or primary node virtual machine configurations will be collected during baseline creation.

Workaround: None.
Fresh deployment of vRealize Business for Cloud integration with vRealize Automation works only when vRealize Automation is added to a private cloud environment before vRealize Business for Cloud
When you add vRealize Business for Cloud to a private cloud environment in vRealize Suite Lifecycle Manager before adding vRealize Automation to the environment, you cannot integrate vRealize Business for Cloud and vRealize Automation.

Workaround: To integrate vRealize Buisness for Cloud with vRealize Automation, add vRealize Automation to the private cloud environment before or at the same time you add vRealize Business for Cloud.
NEW 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 provided when you create the environment for the first time.

Workaround: Generate a single SAN certificate with all the product or management virtual host names or a wild card certificate and provide this certificate when you create the environment for the first time. This ensures support for post provisioning actions such as Add Products and Scale Out.
NEW When you register to My VMware from the VMware vRealize Suite Lifecycle Manager settings page, downloading the product OVA does not work.
This problem happens after you download and deploy the the Lifecycle Manager virtual appliance. When you go to the VMware vRealize Suite Lifecycle Manager settings page at My VMware, downloading the product OVA fails because the proxy is not set. You must configure the proxy for downloading from myVMware.

Workaround: Complete one of these workarounds.

Workaround 1

1. Update the proxy in the /usr/java/jre-vmware/lib/net.properties file.

2. Restart the server.

/etc/init.d/vlcm-server restart

3. Restart Xenon services.

/etc/init.d/vlcm-xserver restart

Workaround 2.

1. In /etc/init.d/vlcm-xserver under JVM_OPTIONS, add -Dhttp.proxyHost= \ -Dhttp.proxyPort= \ -Dhttps.proxyHost= \ -Dhttps.proxyPort= "

2. In /usr/share/tomcat/bin/catalina.sh replace JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS" with JAVA_FLAGS="-Dhttp.proxyHost= -Dhttp.proxyPort= , -Dhttps.proxyHost= -Dhttps.proxyPort= "JAVA_OPTS="$JAVA_OPTS $JSSE_OPTS $JAVA_FLAGS"

3. Restart the server.

/etc/init.d/vlcm-server restart

4. Restart Xenon services.

/etc/init.d/vlcm-xserver restart
vRealize Operations Manager cluster is not accessible after revert the snapshot of vRealize Operations Manager taken by vRealize Suite Lifecycle Manager
vRealize Operations Manager setup is not accessible after revert the snapshot of vRealize Operations Manager as the vRealize Operations Manager cluster in inconsistent state.

Workaround: Take the vRealize Operations Manager cluster offline before taking the snapshot of the vRealize Operations Manager virtual machine.
1. Log in to the vRealize Operations Manager Admin UI and take the vRealize Operations Manager cluster offline.
2. Take a snapshot of the vRealize Operations Manager virtual machine using vRealize Suite Lifecycle Manager via Manage Environment page.
3. Log in to the vRealize Operations Manager Admin UI and bring the vRealize Operations Manager cluster online.
vIDM deployment using vRealize Suite Life Cycle Manager fails when vIDM is downloaded from My VMware using vRealize Suite Lifecycle Manager
When you deploy vIDM using vRealize Suite Lifecycle Manager after downloading vIDM from My VMware using vRealize Suite Lifecycle Manager, the deployment fails with the error message Invalid network in property netmask0.

After vIDM OVAs downloaded from My VMware using vRSLCM, verify the Product Binary name of VMware Identity Manager present at vRealize Suite Lifecycle Manager's Settings page > OVA Configuration tab > Source Location option. If the product binary name contains euc-unified-access-gateway or identity-manager-connector, then that is a wrong mapping.

Correct the OVA source file mapping of vIDM.
1. Browse to OVA configuration tab under the Settings tab.
2. Delete the VMware Identity Manager OVA source entry using delete icon.
3. Select My VMware from Source Location Type dropdown.
4. Select VMware Identity Manager from Product Name dropdown.
5. Select the required vIDM version from Product Version dropdown.
6. Select Install from Product Binary Type dropdown.
7. In the Product Binary dropdown select a ova file name that does not contain euc-unified-access-gateway or identity-manager-connector.
  For example: correct OVA source file name of vIDM : identity-manager-2.9.2.0-6095217_OVF10.ova
8. Click on Save button, this will create a new OVA source file mapping for vIDM installation.