provider/aws: Expose reason of EMR cluster termination

[radeksimko]

This is related to the following test failure from today:

=== RUN   TestAccAWSAppautoScalingTarget_emrCluster
--- FAIL: TestAccAWSAppautoScalingTarget_emrCluster (652.43s)
    testing.go:280: Step 0 error: Error applying: 1 error(s) occurred:
        
        * aws_emr_cluster.tf-test-cluster: 1 error(s) occurred:
        
        * aws_emr_cluster.tf-test-cluster: [WARN] Error waiting for EMR Cluster state to be "WAITING" or "RUNNING": unexpected state 'TERMINATING', wanted target 'WAITING, RUNNING'. last error: %!s(<nil>)

Even though we cannot prevent failures like this we should at least expose the reason of the failure and fail faster.

Related: #13600

Before

(took about 9min 30secs to fail)

• aws_emr_cluster.emr-test-cluster: 1 error(s) occurred:

• aws_emr_cluster.emr-test-cluster: [WARN] Error waiting for EMR Cluster state to be "WAITING" or "RUNNING": unexpected state 'TERMINATING', wanted target 'WAITING, RUNNING'. last error: %!s()

After

(takes about 30sec to fail)

• aws_emr_cluster.emr-test-cluster: 1 error(s) occurred:

• aws_emr_cluster.emr-test-cluster: [WARN] Error waiting for EMR Cluster state to be "WAITING" or "RUNNING": EMR Cluster is terminating. VALIDATION_ERROR: The subnet configuration was invalid: No route to any external sources detected in Route Table for Subnet: subnet-8d91a7ea for VPC: vpc-012dc867

[stack72]

LGTM!

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.