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
Describe the bug
Existing code fails to detect in some cases the presence of an existing fuse mount process, leading to the creation of multiple fuse processes. This is a concurrency issue.
Fix has been identified and is in progress
To Reproduce
Steps to reproduce the behavior:
Create mount for volume X on pod1
Create mount for volume X on pod2
If pod1 and pod2 are on the same node, and created in quick succession, multiple fuse processes for volume X are created
Expected behavior
Additional fuse processes for existing mounts shouldn't be created.
Actual behavior
A clear and concise description of what actually happened.
Environment:
kadalu 1.1
Screenshots or Logs
If applicable, add any screenshots to help explain your problem. Try capturing relevant logs, post them to http://gist.github.com/ and post the links in the issue.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
wdec
changed the title
[Bug]: Issue existing volume mount detection
[Bug]: Dupicate fuse processes/issue with existing volume mount process detection
Aug 30, 2023
Describe the bug
Existing code fails to detect in some cases the presence of an existing fuse mount process, leading to the creation of multiple fuse processes. This is a concurrency issue.
Fix has been identified and is in progress
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Additional fuse processes for existing mounts shouldn't be created.
Actual behavior
A clear and concise description of what actually happened.
Environment:
kadalu 1.1
Screenshots or Logs
If applicable, add any screenshots to help explain your problem. Try capturing relevant logs, post them to http://gist.github.com/ and post the links in the issue.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: