VMware

VMware vCloud Connector Release Notes

vCloud Connector 2.7 | 13 NOV 2014 | Build 2270313 (Server), 2270314 (Node)

What's in the Release Notes

The release notes cover the following topics:

What's New

vCloud Connector 2.7 includes the following updates.

  • Ability to set the synchronization schedule for Content Sync and to synchronize at any time
    You can now specify the schedule for synchronizing subscription folders with published folders. You can select specific days and times, or a time interval, for the synchronization. You can also use the Sync Now option to synchronize folders at any time.
  • Ability to monitor data transfer progress during copy
    For copy tasks, you can view up-to-date data transfer status. You can see how much data has been transferred at each copy stage. The status is refreshed frequently. This information is available for all copy tasks, whether they are initiated with the Copy command, Content Sync, or Stretch Deploy.
  • Limit on concurrent copy tasks
    You can start a maximum of five concurrent copy tasks to or from an on-premise node. This restriction applies to the Copy command only. There is no limit on public nodes.
  • New UDT properties
    Two new properties let you to set the minimum and maximum bandwidth for UDT transfer.
  • Lossless copy
    When you copy a vApp from a source vCloud Director cloud to a destination vCloud Director cloud, and you want to preserve the network configuration of the vApp, that is, its firewall and NAT rules, you can select the Lossless copy option in the Copy wizard. Lossless copy is applicable only if the source and destination vCloud Director clouds have identical Organization, virtual data center, and Organization network names. Note that when you select the Lossless copy option, you cannot select the deploy option. The vApp is always copied to the destination vCloud Director cloud as a vApp template. Deploy the vApp manually from vCloud Director.
  • Improved error reporting
    When a copy task fails, you can view detailed information in the Tasks pane, such as the stage in which it failed.
    Log files have also been improved to provide more details such as the task ID and copy stage, throughput during transfer, and traceroute information.
  • Bug fixes

Upgrade is supported from vCloud Connector 2.6 and 2.6.1. See Upgrading to vCloud Connector 2.7 for information.

Supported Browsers

  • Internet Explorer 8, 9, 10, 11
  • Chrome 22, 23

Supported Platforms

  • vSphere 4.0 update 3, 4.1, 5.0, 5.1, 5.5.x
  • vCloud Director 5.1, 5.5, 5.6.2, 5.6.3, 5.8, 5.9
  • vCloud Networking and Security 5.1.2, 5.1.3, 5.5, 5.5.2

For the latest information about supported platforms, see the VMware Product Interoperability Matrixes.

Note: The vCloud Connector user interface appears as a plug-in in vSphere Client. You cannot use it with the vSphere Web Client.

Documentation

Known Issues

Upgrade

Clear Internet Explorer cache after upgrading vCloud Connector
After you upgrade vCloud Connector, you must clear your Internet Explorer browser cache. You need to do this to ensure that new data is shown in the user interface and in the vCloud Connector server and node Admin Web consoles. Ensure that the Preserve Favorites Website data option is deselected in the Delete Browsing History box when you clear the cache.

Upgrade might fail if you have third-party software installed in a server or node virtual machine
If you have third-party software installed in a server or node virtual machine and it consumes a large amount of the root partition, upgrade might fail.
Workaround
Install vCloud Connector 2.7 directly instead of upgrading.
The root partition size has been increased in vCloud Connector 2.7 to support future upgrades.

Installation and Configuration

Server tab in the Server Admin Web console and Node tab in the Node Admin Web console display a blank page
If you are using Firefox 15 or later, when you select the Server tab in the vCloud Connector Server Admin Web console, a blank page appears. A blank page also appears when you select the Node tab in the vCloud Connector Node Admin Web console.
Workaround
Use a different browser to log in to the vCloud Connector Server and Node Admin Web consoles.

Node or server screen loads for a long time or node cannot be registered with server
After you install and power on a vCloud Connector node or server, or restart it, when you log on to its Admin Web console and click on the Node tab (for the node) or Server tab (for the server), the screen continues to load for a long time. You might also be unable to register the node with the server.

The following error appears in the log file:
Caused by: liquibase.exception.LockException: Could not acquire change log lock.

This problem is likely to occur when you deploy more than one virtual machine from the vCloud Connector server or node OVF template concurrently, instead of waiting for the previous one to finish deploying.

Workaround

  1. Log in to the node or server console as admin. The default password is vmware.
  2. Log in to the node or server database.
    For the node, type the following command: psql hcs postgres
    For the server, type the following command: psql hcs1 postgres
  3. Type the following command: select * from databasechangeloglock;
    The status in the locked column displays t.
  4. Update the locked status to 'false': update databasechangeloglock set locked='false';
  5. Verify the status: select * from databasechangeloglock;
    The status in the locked column now displays f.
  6. Exit the database: \q
  7. Restart the tomcat service.
    For the node, type the following command: /etc/init.d/hcagent-tomcat restart
    For the server, type the following command: /etc/init.d/hcserver-tomcat restart
    When prompted, enter the password vmware.
  8. Log out of the node or server console.

Copy

Upload timeout error while transferring large workloads to vCloud Director-based clouds
Transfer of a large workload from vSphere to a vCloud Director-based cloud fails with the following error: "OVF import failed. An error occurred while uploading the file. Check the upload timeout."
Workaround
Increase the transfer session timeout in the destination vCloud Director cloud.

  1. Log in to the vCloud Director instance as a system administrator.
  2. Click the System tab, then the Administration tab.
  3. In the Administration pane, click General.
  4. Under Timeouts, increase the value of Transfer session timeout.

A backslash or double quotes character in the destination name freezes the user interface at "Validation in progress" stage
In the Copy wizard, if you specify a destination name with a backslash or double quotes character, when you click the Validate button, the user interface is frozen at the "Validation in progress" stage.
This error does not occur if the characters are in the sequence \" at the beginning of the name.
Workaround
Exit the vSphere Client and restart it.

Shared networks of a virtual data center not shown in vCloud Connector wizards
In vCloud Connector wizards that let you select a destination network, such as the Copy wizard, shared networks of a virtual data center do not appear.
Workaround
None.

Copy to vSphere cloud fails with "Folder must not be null" error
When you copy a template with the Deploy option selected, if you select a vApp as the destination resource in the destination vSphere cloud, copy fails with a "Folder must not be null" error.
Workaround
Select a resource pool or cluster/hosts as the resource in the destination vSphere cloud.

Copy and Content Sync fail for vApp templates that have been added to the catalog with the 'Make Identical Copy' option
If, in vCloud Director, you add a vApp connected to an Organization VDC network to a catalog using the Make Identical Copy option, the following issues occur when you use the vApp template with vCloud Connector:

  • If you copy the vApp template to another vCloud Director cloud, the copy task fails.
  • If you subscribe to the catalog that contains the vApp template (and specify a subscription folder on a vCloud Director cloud), the subscription task fails.
The failure occurs when the vApp is being imported to the destination vCloud Director cloud. You get an error message such as the following:
WARN | backend-activity-pool-118 | VAppUploadManagerImpl | Transfer session: 7883d6f8-b81c-4351-9de3-319ad80e1f11. Error during content upload: Following errors occurred while updating network connections: Invalid network parameter: Invalid IP address.

Workaround
If you want to manage a vApp template in vCloud Connector, ensure that the Make Identical Copy option was not used to create the vApp template.

Isolated networks not listed in Copy wizard
When you use the Copy wizard to copy a virtual machine or vApp to a vCloud Director cloud, if you select the deploy option, the Select network configuration field lists the networks in the destination cloud. However, if you have set Stretch Deploy settings on the destination cloud (from the vCloud Connector server Admin Web console), only routed organization networks appear in the list; isolated networks do not appear in the list.
This problem also occurs when you use the Deploy command to deploy a template on a vCloud Director cloud.
Workaround
Unregister the Stretch Deploy settings from the destination cloud before you copy or deploy.
1. Log in to the vCloud Connector server Admin Web console at https://vccServerIP:5480.
2. Click the Nodes tab.
3. Click the gears icon next to the vCloud Director cloud and select Unregister Stretch Deploy Settings.
4. Click OK to confirm.

Copy Wizard does not display a warning for attached ISO file while copying from vCloud Director clouds
vCloud Connector does not support copying objects that have an ISO file attached. When you try to copy an object with an attached ISO file from a vSphere cloud, the Copy wizard displays a warning when you validate your copy selections. However, when you try to copy an object with an attached ISO file from a vCloud Director based cloud, the Copy wizard does not display a warning. When you proceed with copy, the copy task fails.
Workaround
Do not copy objects that have attached ISO files.

Temporary template created during copy validation is not deleted if copy fails
When you copy a template to a vCloud Director cloud, as part of copy validation, a temporary template is created to check permissions on the destination catalog. The temporary template is deleted after the template is copied. However, in some cases when copy fails, the temporary template may not be deleted.
Workaround
Delete such templates manually. Temporary templates are named VccValidationTemplate.

Copy validation does not display error for vSphere Profile-Driven Storage issues
If you copy an object to a vCloud Director cloud whose underlying vSphere instance uses Profile-Driven Storage, and there are any errors related to the Profile-Driven Storage service, vCloud Connector does not detect them during copy validation. Copy validation in the Copy wizard succeeds but the copy task fails. You get the following error when the task fails:
"Remote task failed. Reason : The task has failed. Reason : OVF import failed. 500: Unable to perform this action. Contact your cloud administrator"
Workaround
Resolve the issues, then copy the object again.

Cannot use UDT protocol across two firewalls
If your environment has two firewalls between the source and destination vCloud Connector nodes, you cannot use the UDT protocol to copy data. UDT copy occurs over a dynamically-generated port on the source node and port 8190 on the destination node (or, when you copy between a private cloud and a public cloud, between a dynamically-generated port on the private cloud node and port 8190 on the public cloud node). Any firewall rules must allow for this type of connection for data transfer. In an environment with two firewalls, this type of connection is not possible.
Workaround
None.

UDT copy from a private cloud to a public cloud fails sometimes
In low bandwidth networks, when you copy a large virtual machine or vApp from a private cloud to a public cloud using the UDT protocol, copy might fail. The progress bar displays 30% for a long time, then the copy task fails.
Workaround
In the source and destination vCloud Connector nodes, set properties to configure a smaller UDT packet size.

  1. Log in to the node console as admin.
    The default password is vmware.
  2. Open the /usr/local/tcserver/vfabric-tc-server-standard/agent/webapps/agent/WEB-INF/spring/appServlet/management.xml file in a text editor.
  3. Search for property name="udtProperties".
  4. Edit the following:
    udt_pkt_size: Packet size of UDT packets. The default value is 1048576 KB. For low bandwidth networks, set the value in the following range: 1024-1048576 (1KB to 1MB)
    udt_snd_buf_size: Buffer size of UDT at the source. The default value is 10485760 KB. The value must be greater than udt_pkt_size. The recommended value is approximately 10 times the value of udt_pkt_size.
    udt_rcv_buf_size: Buffer size of UDT at the destination. The default value is 10485760 KB. The value must be greater than udt_pkt_size. The recommended value is approximately 10 times the vaue of udt_pkt_size.

UDT copy fails with a "Could not connect" or "Bind failed" error
UDT copy might fail with a "Could not connect" or "Bind failed" error when the vCloud Connector nodes associated with the source and destination clouds are registered to the vCloud Connector server using fully qualified domain names (FQDN).
Workaround
Use FQDNs with proper entries in the DNS server so that the FQDNs get resolved to the correct address for UDT copy to work.

UDT copy fails with a "Server does not exist" error when FQDNs are used
UDT copy might fail with a "Server does not exist" error if you are using FQDNs for the vCloud Connector nodes and server. When the UDT service is enabled with FQDN, the server address gets resolved to the loopback address (127.0.0.1) instead of the static IP address with which the node is associated. The UDT service starts running on 127.0.0.1:8190 and cannot be reached on its FQDN or IP address.

You can use the following command in the vCloud Connector node console to check for this issue:
netstat -aun
The command returns the following:

"udp 0   0   127.0.0.1:8190   0.0.0.0:*"
Workaround
  1. Log in to the vCloud Connector node console as admin. The default password is vmware.
  2. In the /etc/nsswitch.conf file, change the hosts entry from
    hosts: files dns
    to
    hosts: dns files
  3. Restart the node.
  4. Enable UDT.
  5. Use the following command again:
    netstat -aun
    The command should return the following:
    "udp   0   0   IPaddress:8190 0.0.0.0:*" 

Deploy

Cannot deploy from a template if cloud is added with vApp User role
If you add a vCloud Director cloud to vCloud Connector using a vApp User role, you cannot deploy vApps from templates. You get the following error:
"Access is denied."
Workaround
Use a different user role to add the cloud.

UI

Cannot see virtual data centers when a node is registered with the server using system administrator credentials (vCloud Director only)
If you register a node associated with a vCloud Director cloud with the vCloud Connector server using system administrator credentials, you cannot see any of the virtual data centers or their contents in the UI. Only catalogs and templates are visible.
Workaround
Do the following:

  1. In the Browser panel, expand the cloud.
  2. Reload each organization by right-clicking and selecting Reload.
  3. For vCloud Director 5.1.2 clouds, if all content is still not displayed after you have reloaded the organizations, collapse the tree and reload the cloud.

Content Sync

Deleted published folder or catalog continues to appear in Content Library
When you delete a published folder or catalog from the source cloud, it continues to appear in the Content Library instead of being removed. However, vCloud Connector does not attempt to synchronize subscription folders with the deleted published folder or catalog.
Workaround
Unpublish the folder or catalog from the Content Library. All subscriptions to the folder or catalog will be cancelled.

Initial copy to a subscription catalog on vCloud Director fails with the error "Failure while importing data to cloud. The VCD entity already exists."
When you subscribe to a published folder, all the templates in the published folder are copied to the subscription folder and the folders are subsequently kept synchronized. However, if the subscription catalog is on vCloud Director and there is a naming conflict between a template in the published folder and any template in the vCloud Director instance, regardless of the catalog it is in, the initial copy fails with the following error:"Failure while importing data to cloud. The VCD entity already exists."
This also implies that you cannot have two catalogs on a vCloud Director instance subscribed to the same published folder as it would result in a naming conflict.
Workaround
If you have a naming conflict, rename the template in the published folder before subscribing to it.

Cannot preserve all metadata in published vApp templates
When you subscribe to a published vCloud Director catalog, metadata in the templates is preserved depending upon the credentials with which the clouds containing the published catalog and subscription catalog are registered with vCloud Connector. To preserve all metadata entries, register the clouds with system administrator credentials.
Workaround
If you cannot register the cloud with system administrator credentials, use organization administrator credentials instead. This will not preserve all metadata entries but will preserve the entries that have Read-Write access. For more information on how metadata is preserved during Content Sync, see Using vCloud Connector.

All templates in subscription folders or catalogs deleted if "Remove entities if deleted at publisher" option selected
If you select the Remove entities if deleted at publisher option while subscribing to a published folder or catalog in the Content Library, a template should only be deleted in your subscription folder or catalog when it is deleted in the published folder or catalog.
However, all templates in the subscription folder or catalog are deleted in the following cases if the Remove entities if deleted at publisher option was selected:

  • If you unsubscribe from the published folder or catalog.
  • If the published folder or catalog is unpublished from the Content Library.
  • If the cloud containing the published folder or catalog is deleted from vCloud Connector.
The templates are deleted at the next polling interval.
Workaround
If you do not want templates in your subscription folder or catalog to be deleted, do not select the Remove entities if deleted at publisher option while subscribing to a published folder or catalog.

Delay before subscription tasks are updated
After you use the Subscribe command to subscribe to a folder or catalog in the vCloud Connector Content Library, there might be a delay before the task is updated.
Workaround
Refresh to see the updated task status.

Content Sync does not pick up a vApp template with modified metadata
If you modify the metadata of a vApp template in vCloud Director, vCloud Connector Content Sync will not detect it as a modified vApp template and synchronize it to subscription catalogs.
Workaround
Copy the existing template to a new template in the published catalog and Content Sync will pick it up.

Virtual machine name contains timestamp after synchronization
When a template is synchronized to a subscription folder on vCloud Director, the virtual machine in the vApp has a timestamp appended to the name. The virtual machine name should be the same as the synchronized vApp template name.
Workaround
None.

Datacenter Extension (Stretch Deploy and Reverse Stretch Deploy)

Rename network in vCloud Air OnDemand cloud instance
If you want to stretch deploy to a vCloud Air OnDemand cloud instance that has multiple virtual data centers, you must ensure that the destination virtual data center's Org VDC network has a unique name. Do one of the following for the virtual data center to which you want to stretch deploy:

  • Rename the "DEFAULT_ROUTED_NETWORK" network to a unique name. The name must be unique across all the networks in the cloud instance.
  • Create a new gateway network (routed network) with a unique name. The name must be unique across all the networks in the cloud instance.

VM Network Adapter is changed from VMXNet3 to e1000 after virtual machine is stretch deployed to a vCloud Director 5.1.2 or 5.5 cloud
When a Windows virtual machine that has a VMXNet3 Network Adapter is stretch deployed to a vCloud Director 5.1.2 or 5.5 cloud, the network adapter is changed to e1000.
The virtual machine is then unable to retrieve traffic from the VPN tunnel. This issue also occurs when a virtual machine is reverse stretch deployed.
Workaround
In the destination cloud, power off the virtual machine, modify its NIC type back to VMXNet3, then update the MAC address to match the MAC address of the source virtual machine. If this issue has occurred during reverse stretch deploy, make these changes in the source cloud.

Stretch Deploy wizard displays Edge External Network Interface Name for stretched network field even if vApp network is connected to a Direct Organization network
When you stretch deploy a virtual machine from a vCloud Director cloud to a vCloud, in the Stretch Deploy wizard, the Edge External Network Interface Name for stretched network field appears regardless of whether the vApp network is connected to a Routed Organization network or a Direct Organization network. This field is only required for Routed Organization networks.
Workaround
You only need to specify this field if the vApp network is connected to a Routed Organization network.

Offline Data Transfer

Cannot export objects with mounted media or ISO file attachments from vCloud Director 5.5 or later
If you are exporting from vCloud Director 5.5 or later, export fails for objects that have mounted media or an ISO file attached.
Workaround
If possible, remove the mounted media or ISO file, then export the object.

vApp templates in vCloud Air are created incorrectly after Offline Data Transfer
When you use Offline Data Transfer (ODT) to transfer virtual machines, vApps, or templates to vCloud Air, all objects are transferred to vCloud Air as vApp templates. The following problems have been found with the transferred vApp templates in vCloud Air:

  • Transferred templates display a size of 0 bytes instead of their actual size.
  • You can only deploy one virtual machine from the vApp template. Subsequent attempts to deploy fail.
    • For an object exported without the Deploy option, you can deploy a virtual machine from the template but subsequent attempts to deploy fail.
    • For an object exported with the Deploy option selected and the Keep Catalog option selected, the virtual machine is deployed in vCloud Air and the vApp template is saved in the correct catalog. However, subsequent attempts to deploy the template fail.

Workaround
None.

UI does not display a failed task if the source node goes down or the server cannot reach it during export
If the node associated with the cloud from which you are exporting data goes down or if the server cannot reach it during an export task, the export task fails but the UI does not display a failed task.
Workaround
None.