-
Notifications
You must be signed in to change notification settings - Fork 559
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
[e2e failure] backend images not matching kubernetes resource count,image count 1 kubernetes resource count 0 #5166
Comments
If this happens, the gRPC code Internal is probably not right. It would be cleaner to report Aborted so that there is a retry initiated from the CO. See https://github.com/container-storage-interface/spec/blob/master/spec.md#error-scheme for the common errors. |
According to the error scheme documented in the CSI specification, the Aborted error code should be initiate retries, whereas the Internal error code does not require this behaviour. When an RBD-image is still in-use, it can not be removed. The DeleteVolume procedure should be retried and will succeed once the RBD-image is not in-use anymore. Fixes: ceph#5166 Signed-off-by: Niels de Vos <[email protected]>
The kubernetes-csi/external-provisioner may not have a retry on Aborted error codes? |
@nixpanic it retries for all the error cases, it wont depends on any error codes or message. As user expect it to get deleted |
Reopening as the issue is not fixed |
https://jenkins-ceph-csi.apps.ocp.cloud.ci.centos.org/blue/rest/organizations/jenkins/pipelines/mini-e2e_k8s-1.31/runs/389/nodes/94/steps/97/log/?start=0
The text was updated successfully, but these errors were encountered: