VMware Cloud Director App Launchpad 2.0 | 15 OCT 2020 | Build 17029135

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

App Launchpad 2.0 introduces the following new capabilities:

  • Support for Container Applications
    • In addition to VM applications, App Launchpad 2.0 can display container applications from Helm Charts in the App Launchpad catalog.
    • With App Launchpad, tenant users can launch a container application from a Helm Chart to a Kubernetes cluster. Once launched, users can access their running container applications via their IP address from the My Applications page in App Launchpad. See Launch a Container Application. This feature requires Kubernetes clusters to be managed by VMware Cloud Director Container Service Extension, or VMware vSphere with VMware Tanzu.
    • A service provider adds a Helm Chart to App Launchpad by connecting App Launchpad to the repository where the charts are stored. See Add Applications from Helm Chart Repository.
    • Users can edit the YAML file for the application during the launch process. If the Helm Chart repository defines parameters to be shown in a form field, a form will be displayed during the launch process where the user can edit the parameters before launching the app.
  • Integration with VMware Cloud Marketplace
    • App Launchpad 2.0 introduces the ability to connect to VMware Cloud Marketplace. See Add Applications from VMware Cloud Marketplace.
    • VM applications can be subscribed to and container applications can be pulled to App Launchpad from VMware Cloud Marketplace.
    • The auto-sync feature of VMware Cloud Marketplace can be controlled from App Launchpad. This feature automatically pulls new versions of VM applications when they are made available in VMware Cloud Marketplace.
    • App Launchpad introduces the ability to automatically remove old versions of VM applications when new versions are pulled from VMware Cloud Marketplace using the auto-sync feature.
  • Enhanced Support for Custom Applications
    • Service providers can import custom applications to App Launchpad by providing a URL.
    • Service providers can customize logos, text summaries, version numbers, OS, and category tags of VM applications. See Editing Applications.
  • Application Management Enhancements
    • Service providers can define categories and add apps to categories to assist with catalog management.
    • Service providers can add global custom information for applications. 
    • When editing applications, service providers can use rich content format.
    • Tenant users can filter applications by type in their Applications Marketplace and choose between VM or container applications.
    • Tenant users can deploy VM applications to an NSX-T backed routed network
  • Public API


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

Supported Browsers

 App Launchpad is compatible with the current major and previous major release of the following browsers:

  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge
  • Microsoft Internet Explorer 11

Note: You access App Launchpad by using the VMware Cloud Director service provider admin and tenant portals. The Web browsers that App Launchpad supports depend on the VMware Cloud Director version that you run. 

Product Documentation

In addition to the current release notes, you can use the App Launchpad documentation set at https://docs.vmware.com/en/VMware-Cloud-Director-App-Launchpad/index.html.


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.

  • Bitnami VM applications are in UNKNOWN state after an import from VMware marketplace.

    When the service provider tries to import new apps from a catalog, the apps are consistently in UKNOWN state.


    1. Open the VMware Cloud Director provider portal.
    2. Click on Resources and open the tenant portal for the organization AppLaunchpad.
    3. Click Libraries.
    4. Click Catalog and select the catalog from which you are trying to import a vApp.
    5. Click All Actions, then click Subscribe Settings, and enable the Automatically download the content from an external catalog option.
    6. Click Save, select the catalog and then click SYNC.
      The app status synchronizes between VMware Cloud Director and Marketplace after a short period of time.
  • 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.
  • If you are using VMware Cloud Director 10.2.2 or later, when deploying container applications, the clusters of VMware Tanzu Kubernetes Grid are unavailable.

    When a tenant user attempts to deploy a container application to a cluster of Tanzu Kubernetes Grid instances, the cluster status is Unavailable and the user cannot use the cluster as a deployment target.

    Workaround: To work around this issue, use the edge gateway of VMware NSX-T Data Center to add DNAT rules and allow the App Launchpad server to access the primary nodes of the Tanzu Kubernetes Grid cluster. See Configure External Access to a Service in a Tanzu Kubernetes Cluster.

  • Attempting to delete an application with the FAILED_CREATION status fails with the following error message:

    Failed to retrieve the subscription details.

    The issue occurs when the application is not synchronizing with VMware Marketplace.

    Workaround: To work around this issue, manually synchronize the application with VMware Marketplace.

    1. In the VMware Cloud Director service provider admin portal, open the AppLaunchpad organization in Tenant Portal.
    2. Navigate to Libraries > vApp Templates, select the application, and click Sync.
  • Attempting to publish a catalog to any organization listed on a page beyond the 1000th page of organizations fails with the following error:

    Invalid organization IDs 

    Workaround: To work around this issue, use the VMware Cloud Director service provider portal to publish the catalog to the organization. 

    1. In the VMware Cloud Director service provider admin portal, open the AppLaunchpad organization in Tenant Portal.
    2. Navigate to Libraries > Catalogs, click the vertical ellipsis icon next to the catalog and click Share.
    3. In the Organizations tab, select the organizations to which you want to publish the catalog and click Save.
  • Configuring App Launchpad might fail if you enter a trailing slash in the public address of VMware Cloud Director

    To configure App Launchpad with VMware Cloud Director, you run the alp connect script.

    When running the script, you provide the public URL for your VMware Cloud Director instance as a value for the --url argument.

    If you enter the URL with a trailing slash at the end of the address, the command fails. 

    Workaround: When running the alp connect script, make sure that you do not enter a trailing slash at the end of the URL. For example, enter https://cloud.example.com instead of https://cloud.example.com/.

  • Configuring App Launchpad fails with the following error message:

    Can't find vCD user by alp

    To configure App Launchpad, you run the alp connect script. The script creates the App-Launchpad-Service account in the respective VMware Cloud Director system organization. You specify the service account name in the value for the --sa-user argument. If the service account that you specified exists in the VMware Cloud Director system organization, the operation fails and returns the error message.

    Workaround: To work around this issue, you have the following two options: 

    • Use the VMware Cloud Director service provider admin portal to remove the user that you want to specify as the App-Launchpad-Service account.
    • When running the alp connect script, for the --sa-user argument value, enter an account name that does not exist. The script creates the account for you. 
  • If Java SE JDK 11 is installed on the deployment target machine, installing App Launchpad fails with the following error message:

    error: Failed dependencies:
    java >= 1.8.0 is needed by vmware-alp-2.0.0-38709533.x86_64

    Workaround: To work around this issue, append the --nodeps argument to the installation script. For example, to install App Launchpad to the target machine, run the rpm -ivh --nodeps vmware-vcd-alp-v.v.v-nnnnnnnn.e17.x86_64.rpm command. See Install App Launchpad.

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

    Workaround: To work around this issue, import the SAML or LDAP user again and explicitly assign a role. Do not defer the assignment of a role to the identity provider. For more information, see Import Users in the VMware Cloud Director Tenant Portal Guide.

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

    Workaround: To work around this issue, configure a dedicated RabbitMQ vhost for every instance of VMware Cloud Director.

  • Tenant users cannot deploy container applications to a Kubernetes cluster created by the Container Service Extension for VMware Cloud Director, if the cluster is configured with a routed organization virtual data center (VDC) network.

    The Kubernetes cluster obtains a private IP address from the routed organization VDC network and is not reachable for App Launchpad.

    Workaround: To work around this issue, you have the following two options:

    • Deploy the Kubernetes cluster to a direct network that is reachable for App Launchpad.
    • Deploy App Launchpad to a network that allows for access to the private IP address of the Kubernetes cluster.
  • 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. 

    Workaround: To work around this issue, restart App Launchpad.

  • When you add applications to App Launchpad, the operation fails with the following error message:

    Cannot log into organization AppLaunchpad beacuse it has not been assigned rights.

    You might receive this error when attempting to import applications from VMware Marketplace, or when you upload your custom applications.

    Workaround: To work around this issue, assign the correct VMware Cloud Director rights bundle to the AppLaunchpad organization.

    1. Log in to the VMware Cloud Director provider portal as a system administrator.
    2. Navigate to Administration > Rights Bundles.
    3. Click Default Rights Bundle and click Publish.
    4. Select the AppLaunchpad organization and click Save.

    After the publishing task completes successfully, you can import applications from VMware Marketplace and upload your custom applications.

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