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.

Sign up for GitHub

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

Jump to bottom

In case of out of host capacity errors, all fault domains should be tried before backoff #133

Open
shyamradhakrishnan opened this issue Aug 30, 2022 · 0 comments · May be fixed by #134
Open

In case of out of host capacity errors, all fault domains should be tried before backoff #133

shyamradhakrishnan opened this issue Aug 30, 2022 · 0 comments · May be fixed by #134
Assignees
@shyamradhakrishnan
Labels
bug Something isn't working

Comments

@shyamradhakrishnan
Copy link
Contributor

What happened:
In case of out of host capacity errors, backoff happens without retrying other fault domains

What you expected to happen:

In case of out of host capacity errors, all fault domains should be tried before backoff

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • CAPOCI version:
  • Cluster-API version (use clusterctl version):
  • Kubernetes version (use kubectl version):
  • Docker version (use docker info):
  • OS (e.g. from /etc/os-release):
@shyamradhakrishnan shyamradhakrishnan added the bug Something isn't working label Aug 30, 2022
@shyamradhakrishnan shyamradhakrishnan self-assigned this Aug 30, 2022
@shyamradhakrishnan shyamradhakrishnan linked a pull request Aug 30, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shyamradhakrishnan shyamradhakrishnan

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@shyamradhakrishnan