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

csi-resize is updating successful state even if volume expansion operation is failed #474

Open
digambarpat opened this issue Feb 25, 2025 · 0 comments

Comments

@digambarpat
Copy link

digambarpat commented Feb 25, 2025

Steps to reproduce the issue -

  • I created the PVC with size 10 Gi

  • Updated to 12Gi. it's successfully expanded

  • Then updated to 17Ti (which should fail as we are not supporting volume beyond 16Ti)

  • After I described the PVC, below description is updated in PVC -
    " Waiting for an external controller to expand this PVC
    Normal Resizing 6m12s (x3 over 15m) external-resizer volume.csi.azure.com External resizer is resizing volume pv-a1eb04da-8553-4a23-a164-7efe66020f3d
    Warning VolumeResizeFailed 6m12s external-resizer volume.csi.azure.com resize volume "pv-a1eb04da-8553-4a23-a164-7efe66020f3d" by resizer "volume.csi.azure.com" failed: rpc error: code = DeadlineExceeded desc = context deadline exceeded
    Normal VolumeResizeSuccessful 6m12s external-resizer volume.csi.azure.com "

  • As you can see above, Volume resize is showing failed for Volume csi controller but in the very next line, it's showing for Successful for external-resizer

  • Here, external-resizer is updating wrong status even though volume expand operation is not successful.

Final update operation is done by Resizer which is not correct in case of failure.

Do we need to apply any extra step so that external-resizer will report correct status?

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

No branches or pull requests

1 participant