Flaky integ test where the SubscribeToShardIntegrationTest

[joviegas]

Motivation and Context

• Test cases fail in @setup() stage

< ERROR! java.util.concurrent.CompletionException: software.amazon.awssdk.services.kinesis.model.ResourceInUseException: 
Stream subscribe-to-shard-integ-test-123456789 under account 123456789 
not ACTIVE or UPDATING, instead in state CREATING 
(Service: Kinesis, Status Code: 400, Request ID: ca299ffa-90c6-9006-aa63-1a1ca6eea3b3, Extended Request ID: ABC

• The above log indicates that stream is still in CREATING

Modifications

• Added additional verification by adding a list call to ensure that stream is fully operational

License

• I confirm that this pull request can be released under the Apache 2 license

[L-Applin]

We already have a Waiter waiting for the ACTIVE state, but we are failing because the stream is in the CREATING stage? That seems weird, are we sure this is helping?

[joviegas]

Yeap , I have attached the complete log in the internal issue.
The above log is taken from the codebuild logs.
I have started Integ test too as part of the codebuild

[joviegas]

The additional check will ensure that the actual state is properly reflected in the system and will provide additional time with retry logic rather than immediately failing(same as we retrying the test case when it fails)
I recommend proceeding with this safe approach since the current failure of this test case is unnecessarily blocking the release and creating significant churn.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud