log flood when deleting the volume when clone volume exist #236
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt
Milestone
When clone volume exist and we delete the source volume, the daemonset gets flooded with the error log saying
Here what is happening is since there is a clone volume present, the destroy will fail because of the clone volume. The volume mgmt will keep on trying to delete and keep on failing with the error until we delete the clone volume. This will flood the log with unnecessary error messages.
The text was updated successfully, but these errors were encountered: