add pod.Status.{Reason,Message}
to PodNotAvailable
error
#1223
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.
Signed-off-by: Charly Molter [email protected]
When writing tests using terratest it's useful to figure why a pod
failed to start.
For example we use heavily terratest in our e2e suite. Some tests
are flaky for many possible reasons at the moment we have to switch to using:
WaitUntilPodAvailableE
and use the error to get the pod status.Fix #1222
Add extra info in the error message.
Read the Gruntwork contribution guidelines.
Release Notes (draft)
Added / Removed / Updated [X].
Added context to
PodNotAvailable
error to make troubleshooting easier.Migration Guide