VMware

VMware vCenter Lifecycle Manager 1.0.2 Release Notes

Note: Lifecycle Manager 1.0.2 (LCM) is only compatible with vCenter Server 4.0, VirtualCenter 2.5 Update 3, VirtualCenter 2.5 Update 4, and VirtualCenter 2.5 Update 5.

VMware vCenter Lifecycle Manager 1.0.2 | September 10th 2009 | Build 4415

VMware vCenter Orchestrator 4.0.1 | November 19th 2009 | Build 4502

Release notes last updated on December 2nd 2009.

Check frequently for additions and updates to these release notes.


These release notes cover the following topics:

What's New

VMware vCenter Lifecycle Manager (LCM) 1.0.2 release enhances the performance, robustness, and scalability of LCM and resolves a number of known issues.

The LCM 1.0.2 release runs on VMware vCenter Orchestrator 4.0.1. To run LCM 1.0.2, you must install the version of Orchestrator (4.0.1 Build 4502) that accompanies the LCM 1.0.2 download. If you are running LCM 1.0.2 on Orchestrator 4.0 (Build 4439), you should upgrade to Orchestrator 4.0.1 (Build 4502). See the vCenter Lifecycle Manager 1.0.2 Administration Guide for installation instructions.

Top of Page

Important Patches

LCM 1.0.2 Patch 1 and Patch 2 resolve various functional and security issues. LCM 1.0.2 Patch 2 is cumulative - it includes all fixes from LCM 1.0.2 Patch 1. You can download the Patch 1 and Patch 2 packages from the LCM downloads page.

LCM 1.0.2 Patch 1 Overview

You must install LCM 1.0.2 Patch 1 to resolve incorrect behavior of the power state options for users with the LCM Requester and LCM Tech Requester roles.

To install LCM 1.0.2 Patch 1:

  1. Go to the Orchestrator configuration interface at http://orchestrator_server_ip:8282.
  2. On the General tab, click Install Application.
  3. Click Choose and browse to select the LCM-Hotfix-102_1_0_0_9.vmoapp file.
  4. Click Install.
  5. On the Startup Options tab, click Restart service.

Note: You can verify that the patch was applied successfully by checking that the version of the LCM Web view is 0.3.14 in the Web Views tab of the Orchestrator client.


LCM 1.0.2 Patch 2 Overview

You must install LCM 1.0.2 Patch 2 to provide data encryption and resolve incorrect virtual machine states. When applied, the patch encrypts sensitive data such as domain passwords and license keys in the database. The patch also enhances the Lifecycle Scheduler policy, which fixes the incorrect Need Replier • Missing Virtual Machine states of virtual machines that are available.

You should follow the best practices to install Patch 2 correctly:

  • Make sure that you do not have passwords longer than 70 characters stored in the database. Encryption will fail if the password length exceeds 70 characters.
  • Create a backup of the database before installing the patch.
  • Do not restart the Orchestrator server during the installation.
  • Do not delete any workflows or actions during the installation.

To install LCM 1.0.2 Patch 2:

  1. Go to the Orchestrator configuration interface at http://orchestrator_server_ip:8282.
  2. On the General tab, click Install Application.
  3. Click Choose and browse to select the LCM-102-HotFix_2_0_0_17.vmoapp file.
  4. Click Install.
  5. On the Startup Options tab, click Restart service.

Note: You can verify that the patch was applied successfully by checking that the version of the LCM Web view is 0.3.15 in the Web Views tab of the Orchestrator client.

Top of Page

Prior Releases of Lifecycle Manager

See the Lifecycle Manager 1.0.1 Release Notes.

Top of Page

Known Issues

The following issues are known to occur in LCM 1.0.2:

  • End-user response times might increase as the number of virtual machine requests increases

    As the number of virtual machine requests made increases over time, you might notice a gradual increase in Lifecycle Manager response times. For example, response times that approximate 10 seconds when only a few virtual machine requests are made might increase to approximately a minute by the time several hundred requests are made.

  • Importing a large number of virtual machines might take a considerable amount of time

    If you try to import a couple of thousand virtual machines from a virtual machine folder, the request might take a few hours to complete.

  • Error message displayed when trying to run a restricted workflow

    If you click a custom button that links to a workflow and you do not have sufficient permissions to run that workflow, you receive the following error message: Error while downloading.

    Workaround: Place custom workflows in a category that all users can access. For information about adding custom categories, see the vCenter Lifecycle Manager 1.0.2 Administration Guide.

  • Missing parameter for custom elements

    When you add a custom button to the right pane in LCM, you might not be able to run the associated workflow for the object that you have selected in the left pane, because the object is not automatically passed as a parameter to the workflow.

    Workaround: Edit the custom element properties to include the missing parameter.

    1. Select Start > Programs > vCenter Orchestrator > vCenter Orchestrator Client.
    2. Log in as an administrator.
    3. On the Resources tab, select Applications > Lifecycle manager > CustomWeb > ClientCustom.
    4. Right-click the custom element .html file and select Save to file.
    5. Open the saved file and add objectid="ognl:get('dunes_uri')" before the closing bracket (/>).
    6. Right-click the custom element .html file, select Update resource, and select the edited file.
    7. On the Configuration tab in LCM, click the Custom Element view, and click Reset Cache.

  • Cluster placement requires VMware DRS

    If you want to place a virtual machine in a resource pool from a cluster, you must have VMware DRS enabled for the cluster. If VMware DRS is disabled, you will receive the following error message: Error creating.

  • Changes in LDAP directory settings cause unavailable requests

    If you change the common name of a user in the LDAP directory, the user is unable to access his past requests.

    Workaround: Log in as the LCM Administrator, access the unavailable requests from the Catalog view, and use the Change Rights button to reassign each request to the appropriate user.

  • Change of database might be required if migration fails

    If you encounter an error while trying to migrate your configuration from LCM 1.0.1 to LCM 1.0.2, you might need to set up a new database.

    Note: If you are using the same database for both Orchestrator and LCM, configure LCM to use a separate database. If you set up a new common database, you will lose your Orchestrator configuration settings.

    Workaround: Set up a new separate LCM database or replace the existing one.

    1. Go to the Orchestrator configuration interface at http://orchestrator_server_ip:8282.
    2. Log in as an administrator.
    3. On the Startup Options tab, click Stop service.
    4. If you are using a separate LCM database, delete the existing one.
    5. Create a new LCM database. If you are already using a separate LCM database, use the same name for the new one.
    6. On the Startup Options tab, click Start service.
    7. Start LCM and retry the migration procedure.

  • Problematic migration of Callback workflows

    When you export an LCM 1.0.1 workflow from the Callback category in the Orchestrator Client and try to import it in LCM 1.0.2, you might receive an error that the version of the LCM 1.0.1 workflow is earlier than the version of the corresponding workflow in LCM 1.0.2 and the workflow has not been imported.

    Workaround: Delete the LCM 1.0.2 workflow and import the workflow exported from LCM 1.0.1.

  • Infrastructure and Configuration tabs sometimes do not reload correctly

    If you switch from the Infrastructure or Configuration tabs to a different tab, for example Requests or Reports, and then switch back again, the Infrastructure or Configuration tabs might not reload properly. If you log in as an LCM Administrator, the Infrastructure tab that LCM redirects you to might not load properly. This issue affects both Firefox and Internet Explorer browsers.

    Workaround: Reload the page in your browser until it displays correct information.

  • Problematic resizing of panes under Firefox

    If you use Firefox 3.0.8 or later, you can resize the panes using the vertical divider in the Infrastructure tab only once. If you try to resize the panes again and switch to another tab, the Infrastructure tab becomes unusable when you switch back to it.

    Workaround: Close your browser and open it again for the Infrastructure tab to become usable.

  • Pages not completely loaded when using DNS name to access LCM

    If you access LCM by using the machine's DNS name instead of its IP address, some of the pages might fail to load properly. Refreshing a page that is not completely loaded might resolve the problem.

    Workaround: Use IP address to access LCM.

  • Unavailable type of report with Oracle database

    If you are using an Oracle database, you cannot generate a report for virtual machines that are set to be decommissioned.

  • Setting commissioning and decommissioning dates in the future causes a delay

    If you set a future date for provisioning or decommissioning a virtual machine when you submit a request, the event is delayed by one day. The virtual machine is provisioned or decommissioned at the end of the specified date, instead of the beginning of the date.

  • LCM IT Staff users cannot modify customization attributes

    Users with the LCM IT Staff role do not have access to the Change Request button in the Catalog view. LCM IT Staff users are unable to change the customization template attributes for a virtual machine that has been placed.

  • Incorrect state displayed for deleted virtual machines

    If you use vCenter Server to delete a virtual machine which is registered with LCM, its state in the Catalog view continues to show: Operate • Available. After the Lifecycle Scheduler policy runs, it changes the state of deleted virtual machines to: Need Replier • Missing Virtual Machine.

    Note: The Lifecycle Scheduler policy runs at midnight by default.

  • Possible failure with a large number of concurrent users

    If 30 or more users log in concurrently to an LCM instance using a large LDAP with 500 000 or more users, an error might occur.

    Workaround: Follow the LDAP vendor specific performance tuning guidelines.

  • Top of Page

Resolved Issues

The following issues have been resolved in LCM 1.0.2:

  • If the connection to LDAP is lost, LCM Webviews do not display elements with authorization elements.

  • When you use Mozilla Firefox 3, the initial view in the Web UI does not display correctly. If you click this view, it displays correctly.

  • In VirtualCenter 2.0, when you use a Windows 32-bit template from the Virtual Machine Library and you configure LCM to provide users with guest virtual machines and fixed IP @, dns, and ActiveDirectory, the guest machines cannot join the domain and the request times out.

  • LCM placement operation works with templates with only one NIC.

  • In LCM, on the Login/Credential page, if you enter the domain information and click Submit and click Edit, the login credentials appear. If you log out of LCM and log in with the same user and return to this page, the credentials do not appear.

  • After you choose Configuration > Edit mail notifications and enter an email address, when you press Tab, an update occurs. After you re-enter the address to confirm the entry, no update occurs. When you re-enter the email address for the next role and press Tab, an update occurs but first email field turns red. After you enter the email address twice and click Next, the check is successful.

  • In Edit custom element, when you create a new custom element and try to edit it, a null string appears in the right pane.

  • After you deploy a new virtual machine and power it on, the CPU and memory counters and the graphs appear but if the appliance is rebooted, they do not reappear.

  • In LCM, in the Catalog view, if you select a virtual machine that is powered off, the Connect and Open console options in the right pane can be clicked. If these buttons are clicked, error messages appear.

  • When you log in to LCM as an administrator, and you click the Catalog or Request views, a message about problems with the script on the page appears.

  • Logging in or logging out of the Orchestrator Configurator can trigger HTTP Error 403 User not in required role message.You need to open Orchestrator Configurator again from the Start menu.

  • The default configuration for Orchestrator is different in the LCM Appliance and Windows installations for the HTTPS port. By default, the LCM Appliance uses 443, but the Windows installation uses 8081.

  • The Orchestrator Configurator server uses port 3944 for HTTP connections.

The following issues have been resolved in vCenter Orchestrator 4.0.1:

  • Modifying Orchestrator client security settings makes LCM inaccessible
    If you limit access to the Orchestrator client only to administrators by setting the com.vmware.o11n.smart-client-disabled property to true, you receive the following error message: Error while downloading.

  • Experimental feature might cause performance problems
    The Orchestrator build (4439) that was distributed with LCM 1.0.2 included the experimental Perspectives Web view. It was not recommended to use this feature in a production environment, because it might slow down the Orchestrator authentication process. The Perspectives Web view has been removed from Orchestrator 4.0.1 (Build 4502).
  • Top of Page