-
Notifications
You must be signed in to change notification settings - Fork 24
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
Re-introduce ResourceExhausted
error code for openstack
#97
Conversation
ResourceExhausted
error codeResourceExhausted
error code for openstack
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/invite @kon-angelo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you certain that 403 is only used for quota issues ? The way it is expressed in this PR indicates so, but I am not so sure. Lacking the proper rbac would probably result in the same error. Did you verify it via an experiment ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
What this PR does / why we need it:
As a part of gardener/autoscaler#154,
ResourceExhausted
error code will be returned when no valid host is found in the zone to host the VM.Sample live issue - No. 958
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
After discussions with @kon-angelo and @himanshu-kun, we have concluded that quotas are set per region and so there is no point in introducing early backoff for such errors.
Release note: