Log EMR cluster StateChangeReason on failure#98
Merged
Conversation
Surface Cluster.Status.StateChangeReason.Code and .Message in stdout and in the returned error whenever a cluster fails to reach WAITING. Previously the runner only checked the Code internally (to detect bootstrap-failure retries) and never surfaced the underlying reason, leaving Support blind to failures like 'On the master instance, application provisioning failed' or quota errors where no step logs are produced.
Snyk Docker scan flagged two High-severity Uncaught Exception advisories in transitive AWS SDK Go v2 deps. Bumped: - service/s3 v1.71.1 -> v1.97.3 (SNYK-GOLANG-...-S3-16316411) - aws/protocol/eventstream v1.6.7 -> v1.7.8 (SNYK-GOLANG-...-EVENTSTREAM-16316402) go mod tidy pulled along compatible bumps for aws-sdk-go-v2 core, smithy-go, and a handful of internal/* packages.
Oguzhan Unlu (oguzhanunlu)
force-pushed
the
log-reason
branch
from
d19e104 to
0e0cdfa
Compare
Oguzhan Unlu (oguzhanunlu)
added a commit
that referenced
this pull request
May 22, 2026
* Log EMR cluster StateChangeReason on failure Surface Cluster.Status.StateChangeReason.Code and .Message in stdout and in the returned error whenever a cluster fails to reach WAITING. Previously the runner only checked the Code internally (to detect bootstrap-failure retries) and never surfaced the underlying reason, leaving Support blind to failures like 'On the master instance, application provisioning failed' or quota errors where no step logs are produced. * Bump aws-sdk-go-v2/service/s3 and eventstream for CVE fixes Snyk Docker scan flagged two High-severity Uncaught Exception advisories in transitive AWS SDK Go v2 deps. Bumped: - service/s3 v1.71.1 -> v1.97.3 (SNYK-GOLANG-...-S3-16316411) - aws/protocol/eventstream v1.6.7 -> v1.7.8 (SNYK-GOLANG-...-EVENTSTREAM-16316402) go mod tidy pulled along compatible bumps for aws-sdk-go-v2 core, smithy-go, and a handful of internal/* packages.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR surfaces code and message of EMR failures in stdout, freeing Support from manually checking customers' account.
ref: https://snplow.atlassian.net/browse/PDP-2648