You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a patch worked up for this that includes a test that shows we can hit this if the volumewatcher restarts its goroutine just as a delete happens. For example, if a GC claim is written and as a result the volume is deleted before the volumewatcher can enter the loop in the run function, it'll panic. There's a race condition here around shutting down the volumewatcher goroutine I need to solve before I can get that fix up though.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Reported through our support org:
This is bubbling up from
volume_watcher.go#L208
, which suggests the volume is nil here. A quick look at the code shows we're missing a nil-check atvolume_watcher.go#L120-L121
The text was updated successfully, but these errors were encountered: