Error in GetLoggingConfig The specified service instance could not be found

[lionelmace]

Hi

When re-running the script here, it fails attached the logdna instance. Yet, it was able to attach it the first time and I haven't changed anything after.

Any idea?

module.vpc_openshift_cluster.ibm_container_vpc_cluster.cluster: Refreshing state... [id=c5r5me1f0qelptsqsrn0]
module.vpc_kubernetes_cluster.ibm_container_vpc_cluster.cluster: Refreshing state... [id=c5r5mdif0p9etvedrko0]
module.openshift_sysdig_attach.ibm_ob_monitoring.sysdig: Refreshing state... [id=c5r5me1f0qelptsqsrn0/9ee6afcf-cb32-4c14-a1c4-fd52c8df832a]
module.openshift_logdna_attach.ibm_ob_logging.logging: Refreshing state... [id=c5r5me1f0qelptsqsrn0/bf2510ee-ce3a-4fc5-b32f-344fd097c126]
module.kubernetes_sysdig_attach.ibm_ob_monitoring.sysdig: Refreshing state... [id=c5r5mdif0p9etvedrko0/9ee6afcf-cb32-4c14-a1c4-fd52c8df832a]
module.kubernetes_logdna_attach.ibm_ob_logging.logging: Refreshing state... [id=c5r5mdif0p9etvedrko0/bf2510ee-ce3a-4fc5-b32f-344fd097c126]
╷
│ Error: Error in GetLoggingConfig: Request failed with status code: 400, ServerErrorResponse: {"incidentID":"fef92513-6110-4b33-8e0f-fc989abb0a9a,fef92513-6110-4b33-8e0f-fc989abb0a9a","code":"S0024","description":"The specified service instance could not be found. Enter the name or ID of the service instance that you want to use. To list available instances, run 'ibmcloud resource service-instances'. If you deleted your service instance, you must specify the ID of the instance.","type":"BadRequest"}
│
│   with module.kubernetes_logdna_attach.ibm_ob_logging.logging,
│   on .terraform/modules/kubernetes_logdna_attach/modules/configure-logdna/main.tf line 6, in resource "ibm_ob_logging" "logging":
│    6: resource "ibm_ob_logging" "logging" {

[lionelmace]

This seems to be an intermittent issue. It doesn't occur all the times.

[VaishnaviGopal]

Hi @lionelmace , only the 500 series errors are retryable by IBM Cloud provider and the 400 series error codes are non-retryable. Can you contact IKS team with the incident ID of the above error for further investigation to see why this intermittent issue is being caused?