Fix resource exhausted typo

[ebblake]

What type of PR is this?
Bug fix to the specification.

What this PR does / why we need it:
Inconsistent specs are hard to implement.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce an API-breaking change?:

none

[ebblake]

I found this while trying to determine what error to report. CreateVolume mentions both RESOURCE_EXHAUSTED and OUT_OF_RANGE but without a clear statement of which is better when running out of space; while CreateSnapshot clearly wants RESOURCE_EXHAUSTED but ControllerExpandVolume wants OUT_OF_RANGE. In my view, OUT_OF_RANGE applies to things like "requested size needs to be rounded larger than requested limit" or "limit is smaller than the source volume size" (something you can't fix no matter how often you retry with the same arguments), while RESOURCE_EXHAUSTED is for errors that may or may not be transient if more storage resources are freed up in the meantime). I also note that https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1790-recover-resize-failure/README.md#making-allocatedresourcestatus-not-change-unnecessarily-for-every-error-in-131 mentioned OUT_OF_RANGE but not RESOURCE_EXHAUSTED as a plausible reason to back off the retry loop.

[jdef]

thanks for the PR. please sign the CLA if you've not done so already.

[ebblake]

thanks for the PR. please sign the CLA if you've not done so already.

I have: kubernetes-sigs/contributor-playground#1452
Or is there a different CLA for this project?

[jdef]

Diff. See the Ccla file in top dir

…

On Thu, Jan 23, 2025, 11:29 AM Eric Blake ***@***.***> wrote: thanks for the PR. please sign the CLA if you've not done so already. I have: kubernetes-sigs/contributor-playground#1452 <kubernetes-sigs/contributor-playground#1452> Or is there a different CLA for this project? — Reply to this email directly, view it on GitHub <#578 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR5KLFLII7CT5HTNJAREGD2MEKIDAVCNFSM6AAAAABVTLWL4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJQGMZDIMJVGY> . You are receiving this because you commented.Message ID: ***@***.***>

[ebblake]

Diff. See the Ccla file in top dir

Thanks - I'm chasing down whether Red Hat has already signed such a file, and if so, whether it is blanket for all employees or whether I need to be added to a list.