VMware vRealize Suite Lifecycle Manager 1.2 Release Notes

|

Updated on: 17 April 2018

vRealize Suite Lifecycle Manager 1.2 | 12 April 2018 | Build 8234885

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 1.2

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

What's New in vRealize Suite Lifecycle Manager 1.2

  • Install pre-checker allows you to validate the environment create requests before starting the deployment. Pre-validations include user input, infrastructure resource availability, and product-specific checks.
  • Content lifecycle management allows you to manage the release automation of content such as vRealize Automation Blueprints, vRealize Orchestrator Workflows across multiple environments such as development, staging, production. It allows native source control management integration and dependency management between a cross-referenced content.
  • User interface enhancements in the product settings and environment creation pages. Product binary mapping, environment creation using the configuration file, and grouping user input fields are some of the product pages that have been revamped.

Limitations 

  • 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, those product's VMs will not be managed by vRealize Suite Lifecycle Manager.
  • 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 Automation environment 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.
  • 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 vRealize Suite Lifecycle Manager, delete environment operations and snapshots in the environment fail.
  •  Snapshot for VMs remain in the "in progress" state in vRealize Suite Lifecycle Manager
    • Snapshot for VMs that have device backing are not supported and remain in the "in progress" state in vRealize Suite Lifecycle Manager. vCenter does not support the snapshot for VMs that have device backing
  • 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. 
  • Content management does not capture fields that are marked as secured while capturing vRealize Automation Content.
    • If content has a secure field, like a password that is not present in the plain text, content management does not capture those fields. 
  • You can see multiple catalog app tiles and application links of vRealize Suite Lifecycle Manager after your registration of 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.

Resolved Issues

  • In vCenter, if a duplicate cluster is found inside a data center, only the first cluster is listed in the vRealize Suite Lifecycle Manager install wizard

    In vCenter, if a duplicate cluster is found inside a data center, after vCenter data collection completes, only the first cluster appears in the wizard.

  • If the upgrade of vRealize Suite Lifecycle Manager from 1.0 to 1.1 fails, no error message appears and you must restore to the last known good state from a snapshot.

    Create a snapshot of the vRealize Suite Lifecycle Manager 1.0 working state before you upgrade. If a failure occurs, no indication appears in the UI. 

  • Products upgraded in vRealize Lifecycle Manager 1.1 that are installed in vRealize Lifecycle Manager 1.0 do not get the upgraded version in the View Details page

    vRealize Suite Product versions are not updated in View Details page if the products are installed in 1.0 and upgraded in 1.1.

Known Issues

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

  • Upgrade of vRealize Business for Cloud with vRealize Suite Lifecycle Manager does not upgrade remote data collectors

    When upgrading vRealize Business for Cloud in the cross-region environment with vRealize Suite Lifecycle Manager, the vRealize Business for Cloud remote data collector appliances are not upgraded.

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

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

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

  • 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 vRealize Suite Lifecycle Manager, delete environment operations and snapshots in the environment fail.

    Workaround : None.

  • Link to download the vRealize Suite product support bundle is missing from the vRealize Suite Lifecycle Manager Manage Environments page

    When you click download logs on the Manage Environments page in vRealize Suite Lifecycle Manager, the link to download the support bundle does not appear.

    Workaround: After you click download logs on the Manage Environments page, download the vRealize Suite Product support bundle in the vRealize Suite Lifecycle Manager virtual appliace.

    1. Use SSH to log in to the vRealize Suite Lifecycle Manager virtual appliance with root credentials.
    2. Navigate to /data/support-bundle/ and download the support bundle.
  • After vIDM configuration in vRealize Suite Lifecycle Manager, the vIDM server does not sync users who don't have email address in the user account

    After the successful integration of vRealize Suite Lifecycle Manager with vIDM, users who don't have the email address in the active directory are not synced in the vIDM server.

    Workaround: The vIDM server is configured with default mandatory attributes to be present for active directory users. They are userName, email, firstName, and lastName. To resolve the user sync issue, the vIDM admin must remove the email attribute from the user attributes list.

    1. Log in to vIDM as the system domain admin user.
    2. Click the Identity & Access Management tab.
    3. Click Setup.
    4. Click the User Attributes tab.
    5. Deselect email in the Required column.
    6. Click Manage.
    7. Click Sync Now for the the active directory, and click Sync Directory.
    8. Wait for the affected users to sync in vIDM.
  • Full /data disk causes log bundle downloads, OVA mappings, and product deployments to fail

    All data in the vRealize Suite Lifecycle Manager virtual appliance, such as product binaries and product support log bundles, are stored in the /data folder. The default size of the /data folder is 100 GB. When the size of /data reaches 100 GB, log bundle downloads, OVA mappings, product deployments fail.

    Workaround: Increase the size of /data in the vRealize Suite Lifecycle Manager virtual appliance.

    1. Power off the vRealize Site Lifecycle Manager virtual appliance in vCenter Server.
    2. Edit the vRealize Suite Lifecycle Manager virtual appliance in vCenter to increase the size of the second disk from 100 GB to a higher value.
    3. Power on the vRealize Suite Lifecycle Manager virtual appliance.
    4. Log in to the vRealize Suite Lifecycle Manager virtual appliance.
    5. Run the command df -h to verify that the disk size of /data is increased to the value you specified.
  • 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.

  • 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, those product's VMs will not be managed by vRealize Suite Lifecycle Manager.

    Workaround: None.

  • For the import of a brownfield environment, the delete environment confirmation dialog box does not show the VM list, and the environment card recent activity is not be deleted or grayed out for Organic growth the environment

    For the import of a brownfield environment, if you fail to add a vCenter list, the delete environment confirmation dialog box does not show the VMs that are in that particular vCenter. The environment card from the recent activity home page is not deleted or grayed out for Organic growth environment.

    Workaround: You must manually clean up the VMs.

  • vRealize Lifecycle Manager does not provide options to retry requests that fail due to unsupported password phrases by an individual vRealize Suite product

    If you attempt to update the password of a vRealize Suite product with an unsupported phrase, such as a dictionary word, the password update request is rejected and the corresponding vRealize Lifecycle Manager request fails without enough information for debug.

    Workaround: Tasks that fail due to this issue cannot be debugged in the vRealize Lifecycle Manager UI. Check the logs to determine if this issue was caused by a password failure, check the 'catalina.out' in the vRealize Lifecycle Manager appliance log to understand the exceptions. An alternate workaround is to try the product password update outside of vRealize Lifecycle Manager and observe if the entered phrase is supported.

  • Admin logged into vRealize Operations has Read-Only Access

    If VIDM is integrated with vRealize Suite Lifecycle Manager, when vRealize Operations is deployed from vRealize Suite Lifecycle Manager, administrative privilege are not assigned to the VIDM Admin.

    Workaround: After vRealize Operations is successfully deployed from vRealize Suite Lifecycle Manager:

    1. Log in to the vRealize Operations UI by accessing https:// /ui and by using the local Administratoraccount.The default user name is 'admin' and password is same as the default password provided in vRealize Suite Lifecycle Manager during the vRealize Operations deployment.

    2. Navigate to Administration > Access Control.The necessary additional privileges might be granted to the VIDM Admin. For detailed information on setting up access control in vRealize Operations, see:

  • 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 test and deploy.

    Workaround:  None

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

  • Deployment of vRealize Operations fails  

    vIDM connection to vRealize Operations fails, even if the actual deployment and applying of license of vRealize Operations is successful. 

    Workaround: From the Requests page, try to deploy vRealize Operations. If it still not successful then import the newly deployed vRealize Operations into vRealize Suite Life Cycle Manager.

  • Rerun of Pre-Check fails with an invalid IaaS credential even after verifying the credentials

    After you enable pre-check and submit the create environment, if the pre-check fails then user can resume the wizard from the Request page with a request state as PRE_VALIDATION_FAILED. 
    From the report, if the failure is due to the wrong IaaS credential then rerunning pre-check on updating the windows password in the Product details page still results in the wrong IaaS credential. 

    Workaround: Update the windows password in the product details page at each node level and rerun the Pre-Check.

  • vRealize Operations Manager deployment fails due to incorrect infrastructure details and fails to return error codes or messages on the vRealize Suite Lifecycle Manager UI

    vRealize Operations Manager deployment fails when you provide incorrect infrastructure details such as Wrong DNS or Gateway details without running a pre-check while you create an environment flow.

    When the deployment fails, you might not see the correct cause of deployment failure using the error or code message that appears in vRealize Suite LifeCycle Manager UI, and you might not be able to proceed further with that deployment.

    As a result, you might have to delete the Environment Card from vRealize Suite LifeCycle Manager with all the Products or Nodes that were deployed as part of that environment. 

    Workaround: Run Pre-check so that Infrastructure-related issues are detected and can be corrected before triggering the deployment.

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

    Whenever a content has a secure field, like password that are not present in the plain text, content management does not capture such fields. 

    Workaround: None

  • Resume request fails to load vRealize Automation 7.3 product details

    When a deployment request is saved in vRealize Operations Manager 1.1 and the same request is resumed after upgrading VMware vRealize Operations Manager to 1.2, vRealize Automation 7.3 products details page items does not load. This is due to the change in policies in 1.2.

    Workaround:

    1. Navigate to recent Requests in the Home page and delete the Saved request .
    2. Create a new request for the same deployment.
  • You can see multiple catalog app tiles and application links of vRealize Suite Lifecycle Manager after your registration of VMware Identity manager

    Once you register with VMware Identity manager in vRealize Suite Lifecycle Manager, and you click Update from the Settings > User Management tab multiple times, equal number of catalog app tiles and application links of vRealize Suite Lifecycle Manager are created.

    Workaround: None

  • 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: None

    Recommendation: To avoid deployment failure, analyze the available disk space and select appropriate data store before opting to deploy vRealize Operation from vRSLCM. 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.

  • From vIDM 3.2.1 Groups provided as part Group DN does not sync the users automatically to vIDM

    vRealize Identity Manager 3.2 or later does not automatically sync users under a corresponding groups that are synced through group DN unless they are manually synced  or entitled to an application.

    A relevant error message and retry options is provided in vRSLCM during the deployment of vRealize Identity Manager when the Suite Admin user is also not manually synced.

    Workaround:  Under vRealize Identity Manager Users and Groups tab, trigger user sync under the corresponding group page and click Sync Users  under the Users tab.

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

    Workaround: None