VMware

VMware vCloud Automation Center® 5.2.1 (5.2.4 Build 101) Release Notes

vCloud Automation Center 5.2.1 | 13 MAR 2014 | 5.2.4 Build 101

What's in the Release Notes

The release notes cover the following topics:

What's New

  • First full-installation upgrade since vCloud Automation Center 5.2
    • Incorporates previously released vCloud Automation Center 5.2 Hotfix 1 through 6
    • Installer has two options: fresh installation and upgrade from vCloud Automation Center 5.2 to vCloud Automation Center 5.2.1
  • Improved virtual machine reconfiguration
    • Hot Add support for CPU, memory, and storage in vSphere without reboot
    • Storage size reconfiguration of cloned machine using the Self-Serve Portal
    • Reconfiguration of storage size in vApp component machine
  • Improved vApp provisioning
    • Automatic redirection of vApp into intended organization with NIC configured for another organization in template
  • Improved data management
    • Imported virtual machine no longer deleted when the import process is unsuccessful
  • Improved physical provisioning
    • Ability to format a disk of a specific size
  • vCloud Automation Center 5.2.1 enabled to communicate with vCenter Orchestrator 5.5 without compatibility mode setting

System Requirements and Installation

For information about supported host operating systems, databases, and Web servers, see the vCloud Automation Center Support Matrix.

For additional prerequisites and installation instructions, see vCloud Automation Center 5.2.1 Installation Guide.

Changes to vCloud Automation Center 5.2 Documentation

To access the full set of vCloud Automation Center 5.2 documentation, go to the VMware vCloud Automation Center Documentation page. Select 5.2 from the Select a release menu.

This section provides updates to the following vCloud Automation Center 5.2 guides.

vCloud Automation Center Support Matrix Updates

Update 1

This item is added to the list of supported versions of vCenter Server:
vCenter Server 5.5 Update 1
Located in vCloud Automation Center Support Matrix, Virtualization Platform Support, Hypervisor Management, VMware.

This item is added to the list of supported versions of VMware vCloud Director:
5.5.1
Located in vCloud Automation Center Support Matrix, Cloud Support, VMware.

This item is added to the list of supported task automation engines:
VMware vCenter Orchestrator 5.5
Located in vCloud Automation Center Support Matrix, Integration and Third-Party Support, Task Automation Engines.

vCloud Automation Center Multi-Machine Guide Updates

Update 2 - This new section follows Enable a vApp® Virtual Machine to join an Active Directory Domain in Chapter 3 vCloud Director Integration, vCloud Automation Center Multi-Machine Guide.

Clone an Identical Copy from the vApp Template

You can clone an identical copy of a vApp template in vCloud Director with the custom property VCloud.Template.MakeIdenticalCopy. When set to True, the custom property instructs vCloud Automation Center to ignore the customizations specified in the vApp blueprint selected for provisioning and its vApp Component blueprints. In other words, vCloud Automation Center uses only the vApp template and not the vApp and vApp Component blueprints to provision the vApp and its virtual machines. The only changes from the vApp template are the names of the cloned vApp and its component virtual machines, which are generated from the machine prefix. A vApp and its component machines are provisioned in vCloud Automation Center as an identical copy of the vApp blueprint. The default setting for the custom property is False.

Enter the custom property on the Properties tab of the vApp blueprint you selected when requesting a machine; you can enter the property on the tab directly or as part of a build profile selected on the tab. You can also put the property in a provisioning group that includes the selected vApp blueprint. Using this approach affects all vApp blueprints in the provisioning group.

Table 1 shows the interaction of the custom property VCloud.Template.MakeIdenticalCopy in vCloud Automation Center and the option Make Identical Copy located in the vCloud Director vApp template properties.

Table 1 Property and Template Settings for Make Identical Copy
Make Identical Copy? (vCAC Property) Make Identical Copy? (vApp Template) Result
True Ignored Clone from the vApp template only.
  • Do not configure networks
  • Do not customize hardware
  • Do not change the computer name
  • Do not join vApp virtual machines to the AD domain
Only the names of the vApp machine and its component machine are changed from the template names. The SysPrep custom properties, for example, Sysprep.Identification.JoinDomain, are ignored.
False Selected Clone from the vApp template. Also use the vApp and vApp Component blueprints, but do not configure networks. Use the storage path specified in the vApp Component blueprint, or one specified for a component during a request for a vApp machine. The SysPrep custom properties, for example, Sysprep.Identification.JoinDomain, are recognized.
False Not selected Clone from the vApp template. Also use the vApp and vApp Component blueprints.

Machine Resource Changes Ignored

If the custom property is set to True on the vApp blueprint and an assigned vApp Component blueprint specifies a minimum/maximum range for machine resources (CPUs, memory, or storage), any change you make to those machine resources when using those blueprints to request a machine is ignored. However, you can change the machine resources after provisioning the machine and while it is powered on.

Storage Path Changes Ignored

If the custom property is set to TRUE on the vApp blueprint and an assigned vApp Component blueprint specifies a different storage path than the one specified in the vApp template, the storage path specified in the vApp template prevails. This is also true if you change the storage path for a component when requesting a vApp machine.

Update 3 -This section belongs at the end of Chapter 3 vCloud Director Integration, vCloud Automation Center Multi-Machine Guide.

vCloud Director Integration Extensibility

You can create and deploy a vApp custom workflow from the vCloud Automation Center Designer console or with the Workflow Generator plugin and have vCloud Automation Center execute the workflow during vApp provisioning. To be executed, a vApp custom workflow must be deployed to the Model Manager repository and have the name vCloudCustomizeVMn where n is an integer equal to or greater than 1. After vCloud Automation Center completes its own customizations to the vApp and before the vApp is initially powered on, vCloud Automation Center executes all workflows in the repository that have the name vCloudCustomizeVMn in alphabetical order. Note how this differs from numerical ordering in the following examples that use the same workflow names:

(alphabetical) vCloudCustomizeVM2 > vCloudCustomizeVM236 > vCloudCustomizeVM26

(numerical) vCloudCustomizeVM2 > vCloudCustomizeVM26 > vCloudCustomizeVM236

To see if your workflows ran, search the DEM Worker and Orchestrator logs available in vcac_install_dir\Distributed Execution Manager where vcac_install_dir is the vCloud Automation Center installation directory (typically C:\Program Files (x86)\VMware\vCAC).

vCloud Automation Center Operating Guide Updates

Update 4 - This new section belongs in Creating Blueprints, Chapter 3 Setting Up vCAC and Organizing Infrastructure, vCloud Automation Center Operating Guide.

WIM-Based Provisioning and Static IP Addresses

You can assign static IP addresses to virtual and physical machines in WIM-based provisioning. For this option to be available, a vCloud Automation Center Administrator must have enabled static IP use for your site in the vCloud Automation Center Console with vCAC Administrator > Customization, and Enterprise Administrators must have created at least one network profile. See Managing Network Profiles for information on using network profiles.
With virtual machines, you can select a network profile in the Network section of the New (or Edit) Reservation - Virtual page, or you can specify a network profile and network interface with the VirtualMachine.NetworkN.ProfileName custom property. You can assign the network interface to a virtual network with the VirtualMachine.NetworkN.Name custom property. See "vCAC Reserved Custom Properties" for descriptions of these properties.
With physical machines, you must specify the network profile with the VirtualMachine.NetworkN.ProfileName custom property. You must also specify a value with the VirtualMachine.NetworkN.Name custom property, though vCloud Automation Center does not actually use the value.

Update 5 – Append the following note after the note at the bottom of page 197 that begins, “If vCAC cannot successfully collect data…” in Configuring Agents for Hyper-V and XenServer Virtualization Compute Resources, Chapter 4 Using the vCAC Console, vCloud Automation Center Operating Guide.

Note: After data collection runs successfully on a compute resource, the resource persists in vCloud Automation Center even after it is removed. For example, after data collecting a virtual datacenter in vCloud Director called Org vDC, this compute resource can be removed from vCloud Director as well as from provisioning groups, reservations, and so on in vCloud Automation Center. However, Org vDC will continue to appear in vCloud Automation Center as disabled.

Update 6 - These table entries belong in vCloud Automation Center Reserved Custom Properties, Table 22. Custom Properties Reserved by vCAC, Chapter 5 Customizing vCAC, vCloud Automation Center Operating Guide.

Property Description Type
VCloud.Template.MakeIdenticalCopy When True, clones an identical copy of the vApp template in vCloud Director (as a vApp and virtual machines) and provisions the results in vCloud Automation Center (as a vApp machine and vApp component machines). Ignores all changes specified in the blueprints (networks, hardware, computer name, and joining of the vApp virtual machines to the Active Directory domain). The names of the vApp and its virtual machines are the only changes.
When True, uses the storage path specified in the vApp template during cloning, even if a different storage path is specified in a relevant vApp Component blueprint or for a component during a request for a vApp machine.
When False and if the option Make Identical Copy in the vCloud Director vApp template properties is selected, uses the storage path specified in a relevant vApp Component blueprint or the storage path for a component during a request for a vApp machine.
When False, clones a copy of the vCloud Directory vApp template with changes specified by the vApp and vApp Component blueprints.
external
VMware.SCSI.Type SCSI type of the machine. Use one of the following case-sensitive values:
vSphere only:
  • busLogic. Use busLogic emulation for the virtual disk.
  • lsiLogic. Use LSILogic emulation for the virtual disk (default).
  • lsiLogicSas. Use LSILogic SAS 1068 emulation for the virtual disk.
  • pvscsi. Use para-virtualization emulation for the virtual disk.
  • none. SCSI controller does not exist for this machine.
vCloud Director only:
  • buslogic. Use BusLogic emulation for the virtual disk.
  • lsilogic. Use LSILogic emulation for the virtual disk (default).
  • lsilogicsas. Use LSILogic SAS 1068 emulation for the virtual disk.
VirtualSCSI. Use para-virtualization emulation for the virtual disk.
external
VirtualMachine.Reconfigure.DisableHotCpu When True, a user must allow the virtual machine to reboot after changing the number of CPUs. Selecting None for the power action after reconfiguration is complete returns this error message: “You cannot change # CPUs because the Power Action is set to None.” The user must select a different power action or cancel the reconfiguration.
When False, the user can choose not to reboot the machine after reconfiguration is complete. After the user reconfigures the number of CPUs for a machine, the user selects None for the power action and the machine does not reboot.
external
VirtualMachine.Reconfigure.DisableHotMemory When True, the user must allow the virtual machine to reboot after changing the amount of memory. Selecting None for the power action after reconfiguration is complete returns this error message: “You cannot change memory because the Power Action is set to None.” The user must select a different power action or cancel the reconfiguration.
When False, the user can choose not to reboot the machine after reconfiguration is complete. After the user reconfigures the amount of memory for a machine, the user selects None for the power action and the machine does not reboot.
external

Update 7 - This table entry belongs in Table 2. Guest Agent Properties, Preparing for Virtual Provisioning by Cloning, Chapter 2 Preparing for Provisioning, vCloud Automation Center Operating Guide.

Properties Description
VirtualMachine.NoneNetwork.IPAddressingMode Provisioning vApp into vCloud Director does not connect to the configured network when the vApp template has a NIC card that is not connected to a network. To prevent this, set VirtualMachine.NoneNetwork.IPAddressingMode to either "DHCP" or "POOL." Unsupported input for this custom property defaults to POOL. After making this configuration, the virtual machine connects to the vCloud Director network with addressing mode.

Update 8 - Replace the procedure in Reconfiguring a Machine, Appendix A Reconfigure Machine, vCloud Automation Center Operating Guide with the following procedure.

Reconfiguring a Machine

To request a reconfiguration:

  1. Log in to the vCloud Automation Center console.
  2. Do one of the following:
    • As a machine owner, click Self-Service > My Machines.
    • As a provisioning group manager, click Provisioning Group Manager > Group Machines.
    • As an enterprise administrator, click Enterprise Administrator > Enterprise Machines.
    The machine you want to reconfigure should have the status On or Off with no active reconfigure status.
  3. Point to the name of the machine and click Edit.
  4. Adjust the number of CPUs and amount of memory on the machine on the Machine Info tab.
    The ranges are the same as when you requested the new machine from this blueprint, and are subject to the same approval thresholds.
  5. Add volumes, remove volumes, or increase the size of existing volumes on the Storage tab.

    Note: Reconfigure is not supported for IDE disks.

    • To add a new volume, click Add Volume, specify the Capacity in GB, and click the Save button. Optionally, you can specify a Storage Reservation Policy for the new volume or specify custom properties for the volume.
    • To remove a volume, click the Delete button next to the disk. You cannot remove volume 0.
    • To increase the size of an existing volume, click the Edit button next to the volume, specify a new value for Capacity, and click the Save button. You cannot reduce the size of existing volumes.
    Volume size is limited by the total amount of storage specified in the blueprint. For example, if the blueprint has a maximum storage capacity of 30GB, and you provision a machine with 10GB of initial storage, you have 20GB remaining to allocate to existing volumes or additional volumes.
  6. On the Network tab, you can add network adapters, remove network adapters, edit existing adapters, or view the custom properties set on a particular network adapter.
    • To add a new network adapter, click Add Network Adapter, select the network under Name, and click the Save button. All networks enabled on the machine’s reservation are available. Each adapter on the machine must be connected to a unique network.
    • To remove a network adapter, click the Delete button next to the network adapter. You cannot remove the first network adapter.
    • To edit an existing network adapter, click the Edit button next to the network adapter, select a new network under Name, and click the Save button.
    • To view the custom properties for a particular network adapter, click the View link next to the network adapter and under Custom Properties. The Custom Properties pane opens and displays the name, value, encryption status, and prompt user status of the custom properties assigned to the network adapter.
  7. On the Execution tab, specify additional information about the reconfigure request.
    1. From the Execute request drop-down menu, select an option for when to execute the reconfiguration:
      • Select Immediately to begin the reconfiguration immediately after it is approved.
      • Select Scheduled, to specify a date and time to execute the reconfiguration.
      • Note: The scheduled time is the local time where the vCloud Automation Center web server is located. If you are not in the same time zone as the server, you should calculate the time in the server's location when scheduling a reconfiguration.

      • Select Queue for Owner to put reconfiguration on hold after any necessary approvals until you execute it. For more information, see "Executing an Approved Reconfiguration."
      If the Execute request option is not available, the reconfiguration is executed immediately.
    2. If you want vCloud Automation Center to attempt to shut down the machine safely before reconfiguring, select Shut down machine before reconfigure. If the shutdown operation fails for any reason, the reconfiguration is canceled. If the machine is powered off before requesting the reconfiguration, you can clear the selection for this option. If you do not select this option and the machine is powered on when the reconfiguration begins, vCloud Automation Center performs a hard power-off (the equivalent of pulling the plug) before reconfiguring the machine.
      If the virtual machine is powered on when the reconfiguration begins, it is shut down or powered off before reconfiguring and then powered back on at the end of the reconfiguration. If the virtual machine is powered off when reconfiguration begins, it remains powered off at the end of the reconfiguration process.
    3. Optionally, specify a reason for the reconfiguration. This information is passed along with the request to approvers.
  8. Click OK to submit the reconfigure request.
    An entry appears in the Recent Events pane for the machine owner and the requester (if different), including a brief summary of the reconfigure request, and the request is sent for approval if necessary.

Resolved Issues

vCloud Automation Center 5.2.1

This section describes issues resolved in vCloud Automation Center 5.2.1.

  • Unable to use vCloud Automation Center to increase a virtual machine’s hard disk size
    You can now use the vCloud Automation Center console or the Self-Service console to increase the hard disk size of a vApp component virtual machine. However, you cannot resize fast-provisioned (linked) hard drives.

  • vSphereSnapshotinventory workflow takes a long time to complete and is overlapping with other runs of the same workflow
    Previously, the snapshot data collection workflow use to start at the beginning of inventory data collection and it waited for inventory data collection to finish. This caused the snapshot data collection to waste DEM worker resources. This fix starts the snapshot data collection at the end of vSphere inventory collection to solve this issue.

  • A repository placed behind a load balancer experiences an intermittent failure in reading the security model. Afterwards, all clients are unable to access the model manager services.

    This fix resolves two service failures:

    • Certain error conditions cause a service failure that generates this message: System.Runtime.InteropServices.COMException (0x80070490): Element not found. (Exception from HRESULT: 0x80070490). These conditions eventually recover without intervention.

    • On rare occasions, the security store becomes corrupted and generates this message: System.ArgumentException: Value does not fall within the expected range. This situation can require intervention.

    After upgrading to vCloud Automation Center 5.2.1, these events no longer cause a service failure but generate a warning that identifies a role causing the problem. If errors continue, the problem can be resolved manually. The role could be in a template, provisioning group, or enterprise group. If you edit the template, provisioning group, or enterprise group pages for the role mentioned in the log message, this rewrites the security to the authorization store and might resolve the issue. It is also possible to delete and recreate these objects.
    If the role causing the problem cannot be identified in the user interface, use the following procedure to identify the role:
    1. On the model manager server, open Run, enter AzMan.msc in the Open field, and click OK.

    2. Right click the Authorization Store, and select Open Authorization Store.

    3. Identify the role from the connection string found in the store attribute in the configuration.

    4. Use Windows Explorer to browse for the role by expanding the VMPS application folder to find and expand the scope and underlying role that was identified in the log.

    If the warning message persists and the identified role cannot be found in AzMan.msc, restart all vCloud Automation Center services on all machines. If the warning message still persists, contact Customer Support.

  • Error during import leads to data loss and machines being destroyed in vCenter
    This fixed issue is discussed in the following Knowledge Base article: "Importing virtual machines into vCloud Automation Center fails and the virtual machines are deleted" at http://kb.vmware.com/kb/2066200

This section describes issues resolved in previously released hotfixes. All of the following resolved issues are included in this release.

Hotfix 6

  • Unable to power off a multi-machine vApp with component machines minimal number set to 0.

  • A vSphere virtual machine automatically reboots after being reconfigured
    User can now control virtual machine reboot using the vCloud Automation Center console or the Self-Service console after reconfiguring a machine's CPU or memory.

    Use the following procedure to prevent a vSphere virtual machine from rebooting after reconfiguring the CPU:

    1. Add the custom property VirtualMachine.Reconfigure.DisableHotCpu manually to a blueprint under the Properties tab, and set the custom property to False.
    2. Provision a machine using this blueprint.

    After you have provisioned this machine, use the following procedure to reconfigure the CPU without rebooting the machine:
    1. Edit the machine to change the CPU value.
    2. Select None from the Power Action drop-down menu under the Execution tab.
    3. Click Submit.


    Use the following procedure to prevent a vSphere virtual machine from rebooting after reconfiguring the memory:
    1. Add the custom property VirtualMachine.Reconfigure.DisableHotMemory manually to a blueprint under the Properties tab, and set the custom property to False.
    2. Provision a machine using this blueprint.

    After you have provisioned this machine, use the following procedure to reconfigure the memory without rebooting the machine:
    1. Edit the machine to change the memory value.
    2. Select None from the Power Action drop-down menu under the Execution tab.
    3. Click Submit.

  • CustomizeOS task timeout causes provisioning to fail. Users who have existing templates with the previous guest agent service installed and want to continue to use these same templates must uninstall the previous guest agent service before upgrading to vCloud Automation Center 5.2.1. After the upgrade is complete, Users should install the appropriate new guest agent.

  • Some tasks do not timeout in an agent causing the queue to fill up. Once the queue is full, the agent service is inactive.

  • Unable to reconfigure storage for SCSI disk from the virtual machine menu on the self-service portal.

  • Unable to dispose of virtual machines in a multi-machine service that has a provisioning failure.

  • Unable to dispose of a virtual machine that has pending work items. Upgrading to vCloud Automation Center 5.2.1 does not dispose of previously undisposed virtual machines. Contact Customer Support for information about disposing of these virtual machines manually.

Hotfix 5

  • Using the Self-Service Portal to provision a virtual machine fails if any computer resource has a location specified but no reservations configured.

  • Static IP assignment breaks when using the custom property VirtualMachine.Network0.Name to select a network.

  • If the static IP pool is exhausted on a multi-machine request, the request appropriately fails, but IP addresses that were available before depletion are left as allocated with no associated virtual machine. Any IP addresses allocated without an associated virtual machine prior to updating to vCloud Automation Center 5.2.1 are still affected. A SQL script is required to reclaim these IP addresses.

  • Creating a blueprint in vCloud Automation Center that is based on a vApp template in a public catalog of the vCloud Director 5.5 endpoint causes provisioning to fail.

Hotfix 4

  • Communication between vCloud Automation Center and vCloud Director fails when more than two machines are requested.

  • During IP Address Management (IPAM) workflow, static IP assignment does not include Windows Internet Name (WIN) server address provisioning.

  • Virtual machine disks are deleted after the following sequence of events: a virtual machine is provisioned and reconfigured; the same virtual machine is reprovisioned and then reconfigured.

  • Intermittent DVS errors occur while reprovisioning virtual machines.

  • After reprovisioning a component machine, any attempt to add another component machine results in a property mismatch.

  • Virtual machine is disposed of when multiple virtual machine requests are submitted at once due to vCloud Director provisioning deadlock.

  • Capacity Usage by Group report displays no values for vCloud Director endpoints.

  • User with Administrator privileges is unable to view Global Properties.

  • When using a custom property to pass a custom variable for a certificate, multiple machine requests fail, but single machine requests succeed.

  • Data collection fails in vCloud Automation Center after deleting a resource pool.

  • The BIOS ID is not collected for vCloud Director component machines.

  • Blueprints with multiple Network Profiles fail to provision virtual machines after one of the Network Profiles has exhausted all its available static IP addresses. This happens even though other Network Profiles in the blueprint contain available static IP addresses.

Hotfix 3

  • Any attempt to establish an SSH connection to a host machine without a Fully Qualified Domain Name (FQDN) fails.

  • vCloud Networking and Security data collection fails after vCloud Automation Center creates a vSphere endpoint.

  • During the reconfigure process, a virtual machine sometimes becomes stuck in the reconfiguring state.

  • If you use the destroy option to dispose of a vSphere (vCenter Server) virtual machine while a failure, such as a network outage, occurs, the virtual machine can appear deleted in vCloud Automation Center but the actual virtual machine in vCenter Server remains intact.

    It is possible to configure vCloud Automation Center so that a virtual machine is not removed from vCloud Automation Center unless the virtual machine is also removed from vCenter. vCloud Automation Center retries the destroy request until it removes the virtual machine.

    This functionality requires a global property Agent.RecoverableErrors.DisposeVM. To add this property, open SQL Management Studio, and execute the following SQL script against the vCAC database:

    INSERT [DynamicOps.Core].[GlobalPropertyGroup] ([Name], [Description]) VALUES (N'Agent', N'Agent configuration')
    INSERT [DynamicOps.Core].[GlobalPropertySubGroup] ([GroupId], [Name], [Description]) VALUES (8, N'Errors', N'Error processing')
    INSERT [DynamicOps.Core].[GlobalPropertyItem] ([SubGroupId], [Name], [DisplayName], [Description], [Value], [IsEncrypted], [IsReadOnly], [IsHidden]) VALUES (10, N'Agent.RecoverableErrors.DisposeVM', N'Recoverable DisposeVM Errors', N'Recoverable errors returned from DisposeVM workitem in RegEx format', N'The request failed with HTTP status 400|Unable to connect to the remote server', 0, 0, 0)

    When a failure occurs after adding Agent.RecoverableErrors.DisposeVM, vCloud Automation Center compares the value of the global property with the message returned by the vSphere agent and provides a retry option triggered by the error message specified in the SQL script. Each time a match exists, vCloud Automation Center retries the destroy operation until it succeeds. If a match does not exist the vCloud Automation Center functions as usual.

    Updating Agent.RecoverableErrors.DisposeVM

    The regular expression in the SQL script contains the most common generic error messages returned for failures. You can use the Log Viewer in the vCloud Automation Center console to find other error messages that apply to a failed destroy request and replace the error message text in the SQL script or even the regular expression if necessary. Select the generic part of the error message and avoid specific names or other values that would prevent a match. For example, the string “Unable to connect to the remote server” comes from the full error message "Error processing [DisposeVM], error details: Unable to connect to the remote server."

    To update Agent.RecoverableErrors.DisposeVM:

    1. In the vCloud Automation Center console, click vCAC Administrator > Global Properties.
    2. On the Global Properties page, edit the values for global property Agent.RecoverableErrors.DisposeVM.

Hotfix 2

  • When performing a reconfiguration in vCloud Automation Center that adds a disk to component virtual machines, an additional "LSI Logic Parallel" SCSI controller is added to the virtual machines making some virtual machines unable to boot. You can now set the SCSI controller type when reconfiguring a vApp component machine on the My Machines page. On the Properties tab, enter the VMware.SCSI.Type custom property and specify a value for this custom property described in vCloud Automation Center Reserved Custom Properties table. See Update 6 in Changes to vCloud Automation Center 5.2 Documentation.

  • When a new request for a virtual machine is submitted for approval through vCloud Automation Center but the request is not approved within ten minutes, the request process does not complete.

  • Email confirmation messages are not sent after a provisioning request is approved or rejected.

  • Multiple proxy agents configured with the same name and endpoint cause problems when multiple agents processes the same work item.

  • An echo statement in a guest customization for vCloud Automation Center prevents an agent from performing a batch execution of Windows-based scripts.

  • In a large configuration, the My Machines page in the vCloud Automation Center console sometimes shows a total machine count but no machine details.

  • A pair of custom properties that establish a parent-child relationship between two drop-down menus affects all child drop-down menus whenever any parent field is changed.

  • Custom property drop-down menu is enabled for the vCloud Automation Center console but does not work using vCloud Automation Center.

  • After Changed Block Tracking (CBT) is enabled, the vCloud Automation Center console is unable to add a volume to a virtual machine.

  • If a single compute resource is created with a location but no reservation, all attempts to provision any computer resource fail.

  • The guest agent package does not contain resources that enable SCCM provisioning.

  • The vCloud Automation Center console does not provide an option to connect to a vAPP component virtual machine using Remote Desktop Protocol (RDP).

Hotfix 1

  • You cannot add virtual volumes to virtual machines that have Changed Block Tracking (CBT) enabled.

  • Unable to make an identical copy of a vApp template.

  • You can create and deploy a vApp custom workflow from the vCloud Automation Center Designer console or with the Workflow Generator plugin and have vCloud Automation Center execute the workflow during vApp provisioning. See vCloud Director Integration Extensibility for more information.

  • Unable to select a specific network interface controller (NIC) type for a NIC added to a virtual machine during cloning.

  • The vCloud Automation Center console does not display all custom properties for a virtual machine.

Known Issues

The following items are known issues in this release.

The known issues are grouped as follows:

Installation

  • Remote DEM worker service doesn't start after installation
    The default port for the vCloud Automation Center server is 443. If the vCloud Automation Center server is installed on a different port and the installation certificate for the DEM Worker does not specify the port where the vCloud Automation Center server is installed, the DEM worker does not start.

  • Workaround: Do one of the following:

    • Install the vCloud Automation Center server using the default port 443.
    • Install the vCloud Automation Center using a port that is different from the default and install the certificate for the DEM Worker specifying that port.

Upgrade

  • Upgrading vCloud Automation Center 5.2 to 5.2.1 shows wrong version in Windows Programs and Features
    Upgrading from vCloud Automation Center 5.2 to vCloud Automation Center 5.2.1 uses a patch process. For this reason, the version number does not change for any of the vCloud Automation Center components displayed in Windows Programs and Features after the update is complete. However, a fresh installation of vCloud Automation Center 5.2.1 displays the expected version number in Windows Programs and Features.

  • File access error appears during the upgrade process
    During an upgrade from vCloud Automation Center 5.2 to vCloud Automation Center 5.2.1, the installer sometimes presents an error message about not being able to access a file. This is not a serious problem.

  • Workaround: If you see this error message, close the installer and start the upgrade process again.

  • Windows Preinstallation Environment (WinPE) does not support upgrade from vCloud Automation Center 5.2 to vCloud Automation Center 5.2.1
    You must uninstall WinPE before upgrading from vCloud Automation Center 5.2 to vCloud Automation Center 5.2.1. You must reinstall WinPE after the upgrade process is complete. Follow the directions in "Rebuild WinPE Images," Chapter 5 Upgrading to vCAC 5.2.1, vCloud Automation Center Installation Guide.

Server Configuration

  • AppServiceState fails with this message: Not enough storage is available to process this command
    Error conditions can occur when the .NET workflow execution engine in DEM workers attempts to load a workflow for execution.
    Workaround: Three configuration properties provide a way to fine tune DEM workers to respond efficiently to workflow problems. A DEM worker can be configured to detect when an error condition occurs and to automatically restart so that the work does not stop. A DEM worker can be configured to wait a specified time period for running workflows to finish. Workflows still running when the timeout period ends are cancelled. A DEM worker can also be configured to unclaim a workflow if it fails and return the failed workflow to the DEM orchestrator queue. For this functionality to work, the following properties need to be configured in the DEM worker configuration file located at vcac_install_dir\VMware\vCAC\Distributed Execution Manager\%WorkerInstance%\DynamicOps.DEM.exe.config.

  • Name Display Name Description Value Format
    DEM.FailureExceptions Failure Exceptions The exceptions specified to trigger a DEM stop <add key="FailureExceptions" value="[ExceptiontypeName1]:[MaxFailureCount1]:[ShouldUnclaim1][;ExceptiontypeNameN]:[MaxFailureCountN]: [ShouldUnclaimN]"/>

    Where:

    ExceptiontypeName1 is the name of the exception type seen in an error message. Cut and paste the exception type name here, for example, System.Xaml.XamlObjectWriterException. You can specify multiple exception type names. Valid value: Name of the exception type as it appears in the error message.

    MaxFailureCount1 is the maximum number of times the exception occurs before the DEM stops. For each exception type name, you can specify a MaxFailureCount number. Valid value: A positive integer.

    (optional) ShouldUnclaim1 indicates whether or not the DEM returns the failed workflow to the queue for the next available DEM to execute. For each exception type name, you can specify a value for ShouldUnclaim. Specify TRUE for the failed workflow to return to the queue, or FALSE for the failed workflow not to return to the queue. Valid values: TRUE or FALSE. Default value is FALSE.

    Example:
    <add key="FailureExceptions" value="System.Xaml.XamlObjectWriterException:1" />
    DEM.ClosedownTimeoutSeconds Closedown Timeout Seconds The number of seconds after a specified exception occurs before the DEM stops <add key="ClosedownTimeoutSeconds" value="[TimeoutInSecondsBeforeDEMClosesDown]"/>

    Where:

    TimeoutInSecondsBeforeDEMClosesDown is the number of seconds after the specified exception occurs before the DEM stops. Specify a time interval long enough to ensure that all running workflows finish before the DEM stops. Valid values: A positive integer. Default value: 0.

    Example:
    <add key="ClosedownTimeoutSeconds" value="30" />
    DEM.RestartOnFailure Restart on Failure Trigger a full restart of the DEM <add key="RestartOnFailure" value="[WhetherToRestartDEMonFailure]"/>

    Where:

    (optional) WhetherToRestartDEMonFailure specifies whether the DEM stops or performs a full restart when one of the exceptions specified in FailureExceptions occurs. To specify a full restart requires the DEM service account to have administrative privileges on the machine hosting the DEM. Specify TRUE for the DEM to perform a full restart. Specify FALSE for the DEM to stop. Valid values: TRUE or FALSE. Default value: TRUE.

    Example:
    <add key="RestartOnFailure" value="FALSE"/>

Virtual Machine Management

  • Unable to dispose of a virtual machine that has pending work items after upgrade to vCloud Automation Center 5.2.1
    Upgrading to vCloud Automation Center 5.2.1 does not make it possible to dispose of previously undisposed virtual machines. Contact Customer Support for information about disposing these undisposed virtual machines manually.

  • Expire fails to power off a vApp or virtual machine
    When you manually expire a vApp or virtual machine that has an archive period defined in vCloud Automation Center, vCloud Automation Center fails to destroy the machine. vCloud Automation Center incorrectly reports that the machine has powered off, but it is still on.
    Workaround: Power off the vApp or virtual machine manually in your hypervisor to prevent errors during deletion, and manually delete the vApp or virtual machine in vCloud Director.

  • Virtual machines or vApps that fail the import process no longer appear in the import wizard
    When importing virtual machines or vApps into vCloud Automation Center is unsuccessful, the machines that were not imported no longer appear in the import wizard. This makes it impossible to attempt re-importing the machines or vApps.
    Workaround: Perform an inventory data collection of vSphere and vCloud Director, then re-import the machines.

  • Problem results when a vApp with multiple component virtual machines fails to import one or more component machines
    If a vApp with multiple component virtual machines is imported into vCloud Automation Center, but the import process fails for one or more component machines, each virtual machine that failed the import process cannot be imported into vCloud Automation Center.

  • Destroy operation is unsuccessful in deleting multi-machine provisioned using multi-machine service
    Using the destroy operation in the vCloud Automation Center console to delete a multi-machine sometimes does not delete the multi-machine completely.
    Workaround: If clicking Destroy in the vCloud Automation Center console does not remove the multi-machine completely, click Destroy again.

  • Cannot add a component machine to a multi-machine when there are IP addresses available in different network profile, but no available IP addresses in the network profile from which the IP addresses are allocated to multi-machine
    When a multi-machine is provisioned with IP addresses from a network profile, you cannot add a component machine after the IP addresses in the network profile are exhausted. Adding a new component machine is unsuccessful even if another network profile has unallocated IP addresses.
    Attempting to add a new component machine in this situation generates an error message saying that all of the IP addresses in the network profile have been exhausted.