Getting error Instance provisioning failed: Please contact your operations team providing the following information.during running of Smoketest errand for PCC

[sandeep reddy]

During Smoke test of PCC. apply changes failed with below error

Getting error Instance provisioning failed: Please contact your operations team providing the following information.

[Daniel Mikusa]

From the information you've provided it is not clear what is happening here. The only thing I can say is that in the case of PCC, there seems to be a problem provisioning a new service instance. It's providing you the operator the service instance guid, which you could then use to go look at the Bosh deployment which represents that service instance.

 

See here for how you can take the service instance guid and get the deployment name.

 

https://docs.pivotal.io/p-cloud-cache/1-7/troubleshooting.html#get-deployment-name

 

After that, you can use standard `bosh` commands to investigate further.

 

[sandeep reddy]

Error message from change log

 "description": "Instance provisioning failed: There was a problem completing your request. Please contact your operations team providing the following information: service: p-cloudcache, service-instance-guid: c47d4711-83b9-4ff9-81c0-037b5071aa76, broker-request-id: d0875438-34a5-4680-a662-97dd1bca80e4, task-id: 13518758, operation: create",  

             "updated_at": "2019-05-16T12:37:09Z",  

             "created_at": "2019-05-16T12:08:42Z"  

           },  

           "tags": [],  

           "service_guid": "4d16f791-664a-4ffb-971a-b3bf7d2e7920",  

           "space_url": "/v2/spaces/2524c743-b289-4c98-8d35-23d1e9f2fb1b",  

           "service_plan_url": "/v2/service_plans/77023abf-a8df-4cf6-b9b9-6ad4ae9f0792",  

           "service_bindings_url": "/v2/service_instances/c47d4711-83b9-4ff9-81c0-037b5071aa76/service_bindings",  

           "service_keys_url": "/v2/service_instances/c47d4711-83b9-4ff9-81c0-037b5071aa76/service_keys",  

           "routes_url": "/v2/service_instances/c47d4711-83b9-4ff9-81c0-037b5071aa76/routes",  

           "service_url": "/v2/services/4d16f791-664a-4ffb-971a-b3bf7d2e7920",  

           "shared_from_url": "/v2/service_instances/c47d4711-83b9-4ff9-81c0-037b5071aa76/shared_from",  

           "shared_to_url": "/v2/service_instances/c47d4711-83b9-4ff9-81c0-037b5071aa76/shared_

[sandeep reddy]

Faced the same issue for SCS. Went a head and deleted venerable app

and the issue resolved. What can be work around for this