NOTE: THIS TEMPLATE IS DEPRECATED - we should create GitHub issues u/s

TEMPLATE TODOS:

• clone this issue
• set name
• set flakefinder url
• assign component
  • sig-compute -> CNV Virtualization
  • sig-operator -> CNV Virtualization
  • sig-network -> CNV Network
  • sig-storage -> CNV Storage
• set priority (according to status)
  • red -> critical
  • orange -> major
  • yellow -> normal
• remove the TEMPLATE ISSUE link
• remove this TODO block
• remove assignee (this will auto assign to the manager/tl)

test_name
 
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)

Source: flakefinder_url