fix: SANDBOX-838 check that SocialEvent is in a ready state when WaitForSocialEvent after creation #1071
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.
Description
"TestActivationCodeVerification" failed twice, for now, with
Operation cannot be fulfilled on socialevents.toolchain.dev.openshift.com
. I guess this is happening because when we callWaitForSocialEvent
, we are not checking that the resource was in a ready state. So, when we update the resource right after, the resource is not ready in some edge cases and we do not have the latest version of the resource, causing theOperation cannot be fulfilled on socialevents.toolchain.dev.openshift.com
.Issue ticket number and link
SANDBOX-838