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

Handle simulating conductor readiness #834

Conversation

mrkisaolamb
Copy link
Contributor

Looks like during some async operations we
can simulate readines too fast. To avoid this issue we
should handle this in eventually statement

Looks like during some async operations we
can simulate readines too fast. To avoid this issue
we should handle this in eventually statement
Copy link
Contributor

openshift-ci bot commented Jul 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrkisaolamb, SeanMooney

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 [SeanMooney,mrkisaolamb]

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

@openshift-merge-bot openshift-merge-bot bot merged commit b2aa553 into openstack-k8s-operators:main Jul 24, 2024
6 checks passed
Copy link
Contributor

@gibizer gibizer left a comment

Choose a reason for hiding this comment

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

Thanks @mrkisaolamb for making the job stable . Still we need to go back, understand and refactor how we simulate readyness as this is now all over the place and I'm afraid we will keep chasing similar issues as soon as a new change will be needed in the controllers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants