Error: Timed out after 300.001s. Unable to create a space - TAS Smoke Tests

Products

• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

TAS smoke tests errand fails during tile updates or stemcell upgrades with a timeout error during the space creation phase.

The smoke_tests errand reports Exit Code 1. The following error appears in the task logs:

Failure in Spec Setup (BeforeEach) [301.176 seconds] Application Workflow
Timed out after 300.001s. Unable to create a space. 
Confirm that this user has the 'OrgManager' role for a non-admin account.

Environment

VMware Tanzu Application Service (TAS) for VMs

Cause

This issue typically results from transient environmental latency or backend IaaS delays. If the Cloud Controller or the underlying database cannot complete the cf create-space request within the default 300-second timeout window, the errand fails. In many cases, the user permissions are correct, but the request simply timed out.

Resolution

Here are some options to try to resolve the issue:

1. Rerun the smoke_tests errand.
2. Check system organization quotas to ensure sufficient memory and instance availability using cf org-quota system.
3. Verify network connectivity and latency between the BOSH Director and the Cloud Controller API.
4. Manually delete any orphaned test spaces (e.g., SMOKES-SPACE-####) if the errand fails to clean up after a timeout.

If the smoke_tests errand fails again with the same error, then it might be check the logs of the cloud_controller job to know more about the particular underlying problem.