Service binding in space groups and getting an error finding a service instance after creating it

Products

• VMware Tanzu Platform Core

Issue/Introduction

Service binding in space groups and getting an error finding a service instance after creating it

Resolution

The customer is able to create a service instance using cf10, but subsequent cf service calls fail with "not found" despite the creation reporting "OK". This typically indicates that the resource was either created in a different context (org/space) than the one being queried, or the asynchronous creation failed on the backend without updating the CLI's view.

Likely a context mismatch or a race condition where the service instance creation is asynchronous ("Create in progress"), and the CLI query fails before the resource is fully registered in the Cloud Controller's visible inventory for that space group.

1. Verify Context: Confirm the customer is targeted to the exact same Org Group and Space Group in both the create-service and service commands.

2. Check All Services: Have the customer run cf services (plural) to see if the instance appears in the full list for that space.

3. Inspect via API: Use cf curl /v3/service_instances to see if the instance exists in the Cloud Controller database regardless of the CLI's summary view.

4. Wait for Completion: Since the output stated "Create in progress", ensure the customer waits at least 60 seconds before querying, as backend provisioning in space groups can have higher latency.

5. Debug CLI: Run the commands with CF_TRACE=true to see if the cf service call is reaching a different API endpoint or using different credentials than cf10.

The service instance should eventually appear in cf services or the API response once the asynchronous provisioning completes.