VMware Cloud Director App Launchpad | 20 JAN 2021 | Build 17454834

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of App Launchpad introduces a number of resolved issues and the following enhancements: 

  • NEW! Starting with version, you can run App Launchpad as an extension of VMware Cloud Director service. To work with VMware Cloud Director service, App Launchpad supports the MQTT message bus. When working with VMware Cloud Director service, App Launchpad supports adding and launching VM and container applications. Launching container applications to a Cloud Director service instance requires VMware Cloud Director Container Service Extension 3.0. For more information about the requirements for deploying App Launchpad to an environment of VMware Cloud Director service, see Before You Begin
  • App Launchpad now allows you to use a single RabbitMQ instance to configure with multiple instances of VMware Cloud Director and App Launchpad. See the Communication Between App Launchpad and VMware Cloud Director section in Before You Begin and Deploy App Launchpad.
  • With App Launchpad, tenant users can deploy container applications to a Kubernetes cluster that uses a routed organization virtual data center (VDC) network. For information about the additional configuration, see https://kb.vmware.com/s/article/83215.
  • App Launchpad adds the support for advanced environment configuration. For example, if you plan to add a system proxy for App Launchpad server node to access Internet-facing resources, you can configure Java environments in the dedicated configuration file. See Edit the Runtime Environment of App Launchpad.
  • Starting with version, when setting up the App Launchpad infrastructure, to improve the storage usage efficiency, a thin provisioning storage policy is used when creating the organization virtual data center. The storage policy is not changed for existing provider organizations. A system administrator can manually update the storage policy for the AppLaunchpad organization and the organization data center. 


You can upgrade to App Launchpad from versions 2.0 and 1.0. See Upgrade App Launchpad

Resolved Issues

  • If multiple instances of VMware Cloud Director are connected to a single RabbitMQ virtual host(vhost), App Launchpad operations fail randomly

    During the installation and configuration, App Launchpad registers as an extension service to VMware Cloud Director. When you configure multiple instances of VMware Cloud Director and App Launchpad with a single vhost, requests might be routed to the wrong App Launchpad instance. 

    This issue is now fixed. 

  • Users of VMware Cloud Director that use LDAP or SAML cannot use App Launchpad

    Users that authenticate to VMware Cloud Director through LDAP or SAML, cannot open the App Launchpad plugin. When attempting to access the App Launchpad plugin, the system returns a 403 permission denied error message.

    This issue is now fixed.

  • When you launch an application, the IP address of the workload is not displayed after a successful deployment operation.

    When you launch an application from the VMware Cloud Marketplace, after a successful deployment, the tile of the application does not display the IP address of the workload. 

    This issue is now fixed.

Known Issues

  • Importing OVF applications to a catalog fails with an error

    When you try to import an OVF application to a catalog, the process fails with the following error:

    InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

    1. Login to the App Launchpad server as root or sudo user.
    2. Navigate to the local host file and add a new host mapping for ${public-cloud-director-FQDN} to ${internal-cloud-director-IP}.
    3. To specify the public VMware Cloud Director FQDN in the parameter --url, run the command alp connect again.
    4. Restart the App Launchpad service by running the command systemctl restart alp.
  • App Launchpad cannot connect to VMware Cloud Director version 10.3 or later via the AMQP SSL port

    When VMware Cloud Director 10.3 or later configures the extensibility with the RabbitMQ SSL port, the connection between App Launchpad and VMware Cloud Director via the AMQP SSL port fails.


    1. Navigate to the App Launchpad server machine and open the file /etc/ALPEnvironments.
    2. Change the value of the following keys to true and save.


    3. Restart App Launchpad by using the systemctl restart alp command.

    As an alternative, you can configure VMware Cloud Director extensibility with non-SSL port.

  • New Bitnami VM applications are not imported successfully from VMware Marketplace

    If you import Bitnami VM applications to multiple VMware Cloud Director sites from VMware Marketplace, and in the catalog selection, you choose or create catalogs with the same name, the import fails.

    Workaround: On different VMware Cloud Director sites, use different catalog names during app import.

  • You cannot list Kubernetes clusters created in VMware Cloud Director 10.3 when you launch a container

    When you launch a container in App Launchpad and you are running VMware Cloud Director 10.3, you cannot see the Kubernetes clusters in the drop-down menu. The Kubernetes clusters that were created before you upgraded to VMware Cloud Director 10.3 are not affected.

    Workaround: None.

  • You cannot reinstall or upgrade App Launchpad to VMware Cloud Director 10.3

    When you try to reinstall or upgrade an existing App Launchpad instance to VMware Cloud Director 10.3, during the diagnose step of the process, the following error occurs:

    can’t find the upload link in the response header to upload when installing plugin!


    1. Uninstall the App Launchpad UI plugin from the VMware Cloud Director provider portal's Customize Portal plugin.
    2. Run the App Launchpad installation again.
  • App Launchpad Service cannot connect to the external network from the local network interface

    App Launchpad Service cannot connect to the external network from the local network interface and the following error occurs in the Activity Log:

    com.vmware.alp.error.RestClientException: {"status":500,"code":"ERROR_INTERNAL_SERVER_ERROR","message":"An internal server error has been encountered.","resource":"/api/alp/v1/csp-refresh-token","details":{"cause":"I/O error on POST request for \"https://console.cloud.vmware.com/csp/gateway/am/api/auth/api-tokens/details\": console.cloud.vmware.com: Name or service not known; nested exception is java.net.UnknownHostException: console.cloud.vmware.com: Name or service not known"}}

    Workaround: None.

check-circle-line exclamation-circle-line close-line
Scroll to top icon