[sig-storage] virtiofs VirtIO-FS with multiple PVCs [Serial] should be successfully started and accessible with passt enabled (unprivileged virtiofsd) and
[sig-storage] virtiofs VirtIO-FS with multiple PVCs [Serial] should be successfully started and accessible (unprivileged virtiofsd)
are failing reliably on the periodic-kubevirt-e2e-k8s-1.26-sig-storage-root lane since 2023-11-15
 
As the assignee, review the issue and decide on one of the following actions:

• The flake is a critical bug -> Fix the bug immediately, move this issue to in "In Progress", and keep it open until the testcase does not fail anymore
• The flake is non-critical -> Quarantine it (assigning [QUARANTINE] tag to test name), close this issue, and create a follow up to take the issue out of quarantine
• There was an infrastructure issue (anything "below" the testcase) -> Move the issue to "Obsolete"

Important: After the flake has been fixed, document the learning from it inside the fix PR, adding a paragraph to github.com/kubevirt/kubevirt/docs/flake-history.md (not yet existing)

Sources:

• https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-11-20.html#%5bsig-storage%5d%20virtiofs%20VirtIO-FS%20with%20multiple%20PVCs%20%5bSerial%5d%20should%20be%20successfully%20started%20and%20accessible%20with%20passt%20enabled%20%28unprivileged%20virtiofsd%29
• https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flake-stats-14days-2023-11-20.html#%5bsig-storage%5d%20virtiofs%20VirtIO-FS%20with%20multiple%20PVCs%20%5bSerial%5d%20should%20be%20successfully%20started%20and%20accessible%20%28unprivileged%20virtiofsd%29