Troubleshooting Tanzu Operations Manager on Azure

This topic describes how you can troubleshoot known issues when deploying or running VMware Tanzu Operations Manager on Azure.

Installation issues

This section describes how to troubleshoot known installation issues.

Cannot copy the Tanzu Operations Manager image

Symptom

You cannot copy the Tanzu Operations Manager image into your storage account as part of Step 4: Boot Tanzu Operations Manager in Deploying Tanzu Operations Manager on Azure.

Explanation

You have an outdated version of the Azure CLI. You need Azure CLI v2.0.0 or later. To display your current Azure CLI version, run:

az --version

Solution

Install the Azure CLI v2.0 by following the instructions for your operating system in Install the Azure CLI in the Microsoft Azure documentation.

Deployment fails at “create-env”

Symptom

After you click Review Pending Changes, then Apply Changes to install Tanzu Operations Manager and VMware Tanzu Application Service for VMs (TAS for VMs), the deployment fails at create-env with an error message similar to the following:

Command 'deploy' failed:
  Deploying:
    Creating instance 'bosh/0':
      Waiting until instance is ready:
        Starting SSH tunnel:
          Parsing private key file '/tmp/bosh_ec2_private_key.pem':
            asn1: structure error: tags don't match (16 vs {class:3 tag:28 length:127
            isCompound:false}) {optional:false explicit:false application:false
            defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} pkcs1PrivateKey @2
			===== 2016-09-29 16:28:22 UTC Finished "bosh create-env"
			/var/tempest/workspaces/default/deployments/bosh.yml";
			Duration: 328s; Exit Status: 1
Exited with 1.

Explanation

You provided a passphrase when you created your key pair in Step 4: Boot Tanzu Operations Manager in Deploying Tanzu Operations Manager on Azure.

Solution

Create a new key pair with no passphrase and do the installation again. For more information, see Step 4: Boot Tanzu Operations Manager in Deploying Tanzu Operations Manager on Azure.

Insufficient external database permissions

Upgrade issues can arise when the external database user that was used for the network policy database is given insufficient permissions. To avoid this upgrade issue, ensure that the Network Policy Server database user has the ALL PRIVILEGES permission.

Operation issues

This section describes how to troubleshoot known operation issues.

Slow performance or timeouts

Symptom

Developers suffer from slow performance or timeouts when pushing or managing apps, and end users suffer from slow performance or timeouts when accessing apps.

Explanation

The Azure Load Balancer (ALB) disconnects active TCP connections lying idle for over four minutes.

Solution

To mitigate slow performance or timeouts, the default value of the Back end request and idle timeout field is set to 900 seconds. This default value is set high to mitigate performance issues but operators can tune this parameter to fit their infrastructure.

To edit the Back end request and idle timeout field:

Go to Tanzu Operations Manager Installation Dashboard.
Click the TAS for VMs tile.
Click Networking.
Enter your desired time, in seconds, in the Back end request and idle timeout text box.
Click Save.

Service instance creation times out

Symptom

You are unable to provision a service instance of a Java or Go service. Running cf create-service fails with error Failure provisioning service instance... Timed out after 8 minutes... or similar.

Explanation

HTTP libraries for Java and Go, running with default settings, prune connections that have been idle for 240 seconds from their connection pool without sending a TCP reset message back to the client service broker. This removes the ability of the broker to provision new service instances.

Solution

In the Networking pane of the TAS for VMs tile, enter a value of 240 or less in the the Front end idle timeout field, so that Tanzu Operations Manager regenerates the front end connection before it times out.