Cloud Service Broker for AWS - registry.opentofu.org/hashicorp/aws: failed to instantiate provider

Products

• VMware Tanzu Application Service
• VMware Tanzu Application Service
• VMware Tanzu Application Service for VMs
• Ops Manager

Issue/Introduction

Customer is seeing this broker failure:

"errors":"\nError: Failed to load plugin schemas\n\nError while loading schemas for plugin components: Failed to obtain provider\nschema: Could not load the schema for provider\nregistry.opentofu.org/hashicorp/aws: failed to instantiate provider\n\"registry.opentofu.org/hashicorp/aws\" to obtain schema: timeout while waiting\nfor plugin to start..\n"

 

Error: Failed to load plugin schemas Error while loading schemas for plugin components: Failed to obtain provider schema: Could not load the schema for provider registry.opentofu.org/hashicorp/aws: failed to instantiate provider "registry.opentofu.org/hashicorp/aws" to obtain schema: timeout while waiting for plugin to start..

 

Resolution

The OpenTofu (in-place replacement for Terraform) errors that the customer were seeing happen at the point when OpenTofu attempts to launch the necessary providers which are included in Cloud Service Broker as a separate process.

From investigating Terraform and OpenTofu issues we think that this can be caused by a lack of resources for the processes.

Our current recommendation are:

• Monitor the memory usage of the CSB app if possible. This would allow us to see a correlation between high memory usage and these errors occurring.

• It is possible to increase the memory allocation for the CSB app. This can be done through the tile Service Broker Config > Memory limit . The memory needs of the broker app can increase depending on the load of the app.