The Healthwatch CF CLI tests are failing to cf push, start, stop, etc. The pas-sli-exporter VM logs show a timeout exception
pas-sli-exporter/pas-sli-exporter.stdout.log:
API endpoint: https://api.example.com
API version: 3.207.0
user: healthwatch_sli_test
org: system
space: healthwatch2
[1m2026-04-16 01:55:16[m [33mWARN[m [2msliTests.SliTestRunner[m [parallel-1] Caught Exception in task push
java.util.concurrent.TimeoutException: null
at java.util.concurrent.FutureTask.get(Unknown Source) ~[?:?]
at io.pivotal.healthwatch.sliTests.CommandRunner.runCommand(CommandRunner.kt:36) ~[sli-tests.jar:?]
at io.pivotal.healthwatch.sliTests.SliTestRunner$SliTask.run(SliTestRunner.kt:151) ~[sli-tests.jar:?]
...You may also get timeout errors when pushing apps with the CF CLI
Elastic Application Runtime
This can be caused by an issue with the blobstore. Check the cloud controller logs for more information
For example, the following errors might be seen in cloud_controller_ng/cloud_controller_ng.log:
{"timestamp":"2026-04-16T03:01:47.411500302Z","message":"Error with blobstore: Excon::Error::Timeout - connect_read timeout reached","log_level":"error","source":"cc.error_handling_client","data":{"request_guid":"a8c7eb8f-9ac0-40a6-9523-4cb5efe1e5ae"},"thread_id":52740,"fiber_id":52760,"process_id":15,"file":"/var/vcap/data/packages/cloud_controller_ng/92d7d659de40379c5338efd8fd68d7cbdd4b0153/cloud_controller_ng/lib/cloud_controller/blobstore/error_handling_client.rb","lineno":67,"method":"rescue in error_handling"}
{"timestamp":"2026-04-16T03:01:47.412384300Z","message":"Request failed: 500: {\"description\"=\u003e\"Failed to perform blobstore operation after three retries.\", \"error_code\"=\u003e\"CF-BlobstoreError\", \"code\"=\u003e150007, \"test_mode_info\"=\u003e{\"description\"=\u003e\"Failed to perform blobstore operation after three retries.\", \"error_code\"=\u003e\"CF-BlobstoreError\",This errors show that cloud controller timed out trying to connect to the blobstore. This indicates the blobstore was down or there was an issue with the network between cloud controller and the blobstore.
If you are using the internal blobstore, check the nfs_server VM status and logs.
If you are using an external blobstore, check with your network team or cloud storage provider to investigate why cloud controller can't connect to it.