Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: SANDBOX-838 check that SocialEvent is in a ready state when WaitForSocialEvent after creation #1071

Merged

Conversation

rsoaresd
Copy link
Contributor

@rsoaresd rsoaresd commented Nov 25, 2024

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 the Operation cannot be fulfilled on socialevents.toolchain.dev.openshift.com.

Issue ticket number and link

SANDBOX-838

Copy link
Contributor

@mfrancisc mfrancisc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great catch 👍

Copy link

openshift-ci bot commented Nov 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexeykazakov, mfrancisc, rsoaresd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [alexeykazakov,mfrancisc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rsoaresd rsoaresd merged commit a0ddb4b into codeready-toolchain:master Nov 25, 2024
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants