VMware

VMware vCenter Lifecycle Manager 1.2 Release Notes

Note: Lifecycle Manager 1.2 (LCM) is only compatible with vCenter Server 4.0 Update 2 and vCenter Server 4.1.

VMware vCenter Lifecycle Manager 1.2 | August 12th 2010 | Build 280718

VMware vCenter Orchestrator 4.1 | July 13th 2010 | Build 581

Release notes last updated on August 12th 2010.

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.2 release enhances the performance, robustness, and scalability of LCM and resolves a number of known issues.

The LCM 1.2 release runs in a 64-bit environment and adds the following new functionality:

  • Support for vSphere features
    • Thin Provisioning
    • VMXNET3 network adapter
    • vNetwork Distributed Switch
  • Support for Cisco Nexus 1000V
  • Customization of Windows 7 guest operating systems
  • Support for Internet Explorer 8 and Firefox 3.6.x

The LCM 1.2 release runs on VMware vCenter Orchestrator 4.1. To run LCM 1.2, you must install the version of Orchestrator (4.1 Build 581) that accompanies the LCM 1.2 download. See the vCenter Lifecycle Manager 1.2 Installation and Configuration Guide for installation instructions.

Top of Page

Internationalization (I18N) Support

LCM 1.2 complies with I18N Level 1. Although LCM is not localized, it can run on non-English operating systems and handle non-English text. However, LCM does not support local currency and local date format.

Top of Page

Prior Releases of Lifecycle Manager

See the Lifecycle Manager 1.1.1 Release Notes.

Top of Page

Known Issues

The following issues are known to occur in LCM 1.2:

  • Custom LCM 1.1 workflows must be updated to work with LCM 1.2

    Because LCM 1.1 works with the VMware Infrastructure 3.5 plug-in and LCM 1.2 works with the vCenter Server 4.1 plug-in, you must refactor the callback workflows that use objects from the VMware Infrastructure 3.5 plug-in to make them compatible with the vCenter Server 4.1 plug-in, before you can use them in LCM 1.2. For information about refactoring, see the vCenter Orchestrator 4.1 Developer's Guide.

  • Forcing plug-in reinstallation does not affect the LCM configuration

    You cannot reset the LCM configuration by clicking the Reset current version button on the Troubleshooting tab in the Orchestrator configuration interface. The LCM configuration is stored in a database and is not affected by plug-in reinstallation.

    Note: You should not use the Reset current version button. Forcing plug-in reinstallation might cause problems with LCM.

  • Not all infrastructure elements are selectable during manual placement

    When you click the Check Infrastructure button on the Placement view, a list of infrastructure elements, matching the criteria selected for the request, appears. However, only the infrastructure elements for which a possible deployment scenario exists, can be selected when you try to deploy a virtual machine from the Setup button on the Placement view.

  • Customization changes during placement do not take effect

    If you try to change the customization template for a virtual machine during the placement procedure, the changes do not take effect. The virtual machine is deployed with the customization template settings selected during the request procedure.

  • Incorrect network element is selectable when registering a port group

    When you register a port group on a distributed virtual switch, uplink group elements are selectable. You must not select an uplink group instead of a port group on a distributed virtual switch. If you register an uplink group, all virtual machines that use the uplink group will not have network connectivity.

  • Incorrect network label for virtual machines on a distributed virtual switch network

    If a virtual machine is placed on a distributed virtual switch network, the network label is incorrectly displayed as: 'null, <IP_address>' in the Virtual Machine Information pane on the Catalog view.

  • Using Firefox on Linux to access the LCM Web console can cause problems with the console plug-in

    There are a number of possible issues and solutions:

    • In Firefox 3.6.x on Linux, the console plug-in might not load correctly and the console page appears blank, if file permissions are limited. To resolve the issue, navigate to the console plugin installation folder at:
      /<Firefox_profile_folder>/extensions/VMwareMKSNPRTPlugin@vmware.com/plugins/ and run the command "chmod 755 *" to manually enable permissions on the files of that folder.
    • In Firefox on Linux, if error messages appear when you try to use a virtual machine's console or the console installation page opens again after the console plug-in has been installed, you might not have all required libraries installed. For RHEL 64bit, you need to install compat-libstdc++-33-3.2.3 on the setup (ideally using yum, which also installs libstdc++.so.5), and for Ubuntu, go to http://packages.debian.org/stable/base/libstdc++5 and install the missing library.
    • If Firefox reports LoadPlugin: failed to initialize shared library /root/.mozilla/plugins/libmks.so [libexpat.so.0: cannot open shared object file: No such file or directory], create a soft link to libexpat.so.
    • If Firefox reports that it could not install the plug-in (Cancelled -227), create a directory named "plugins" in $HOME/.mozilla on the client computer. Install the plug-in and restart Firefox.

  • Non-ASCII characters cause problems with reports

    If you open an XML report that contains non-ASCII characters with a browser or an XML editor, an error message appears.

    Workaround: Save the report as an .xml file, open the file with a text editor, and change the encoding from 'UTF-8' to 'Windows-1252'.

  • Problematic change of authorization groups

    If you try to run the Edit Authorization Groups workflow with a user who is not a member of the vCO Admin group, specified in the Orchestrator configuration interface, the workflow fails.

    Workaround: Log in to the Orchestrator client as a user who is a member of the vCO Admin group and run the Edit Authorization Groups workflow.

  • Powering on a virtual machine after creation requires VMware Tools

    If you submit a virtual machine request with the option to start the virtual machine as soon as it is provisioned, the state of the request is changed to Error Creating if VMware Tools is not started.

    Workaround: Log in as an LCM Administrator, access the request from the Catalog view, and use the Change State button to change the virtual machine state to Operate Available.

  • Possible increase in server response time

    After heavy continuous usage, for example, after adding a large number of virtual machines or if many users are continuously using the product at the same time, the server response time might increase.

    Workaround: Restart the Orchestrator server.

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

    If you try to import a very large number of virtual machines (for example, one or two thousand) from a virtual machine folder, the request might take a few hours to complete.

  • Error message displayed when trying to run a restricted workflow

    When you click a custom button that links to a workflow, if 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.2 Administration Guide.

  • 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 receive the following error message: Error creating.

  • Changes in LDAP directory settings cause past requests to become unavailable

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

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

  • 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, you can resize the panes by 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.

  • Problematic sorting under Internet Explorer 6

    If you use Internet Explorer 6, you can only sort 9 or less elements by name under the Reports, Configuration, and Administration tabs. If you try to sort 10 or more elements by name, you receive the following error message: Object doesn't support this property or method.

  • Misleading JavaScript error message under Internet Explorer 6

    If you use Internet Explorer 6 with script error notifications enabled, you receive an Operation aborted error message when you open the element selector by clicking a magnifying glass icon. However, you can use the element selector that opens.

    Workaround: Click OK to close the error message and continue your task.

  • Incorrect state displayed for deleted virtual machines

    If you use vCenter Server to delete a virtual machine that 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 that uses a large LDAP with 500 000 or more users, an error might occur.

    Workaround: Follow the performance-tuning guidelines specific to the LDAP vendor.

  • Top of Page

Resolved Issues

The following issues have been resolved in LCM 1.2:

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

  • Missing netmask option

    When you try to create a subnet when editing an existing network, the netmask field is missing.

  • Modifying disk shares of a powered on virtual machine causes an error

    If you submit a request to change the disk shares of a powered on virtual machine and the request is approved, an Error occurred. Shaping changes message appears and the request remains in an Apply changes state.

  • Incorrect virtual machine placement with a dvPortGroup network

    If you try to place a virtual machine in a dvPortGroup network on an LCM instance that uses vCenter with a dvSwitch configuration, the virtual machine is placed incorrectly. The virtual machine is not placed in the dvPortGroup under dvSwitch, but is instead placed in a network named dvPortGroup. Also, the network label of the virtual machine is incorrect.

  • Top of Page