Add upstream patch to kubevirt to force hp-volume- pod to respect blockdevices (IcM 467224770)

[sharath-srikanth-chellappa]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?

This PR is required because of an IcM (https://portal.microsofticm.com/imp/v3/incidents/incident/467224770/summary) titled KubeVirt hotplug "addvolume" failures

Under moderate to heavy load, KubeVirt hotplug volume attachment event fail. We believe this is the result of a problem with how pods are rendered, there is an upstream fix in the latest version to fix this - https://github.com/cwedgwood/kubevirt/commit/af25759a3205ac3cdf42254923e3e20cf336a4a0.patch

Bug 6839 Nexus Cloud; KubeVirt virt-operator has persistent volume attachment problems with hotplug (azure.com)

Change Log

• • Add patch for render hp-volume- pod to respect blockdevices (IcM 467224770)

Does this affect the toolchain?

NO

Associated issues

Links to CVEs

Test Methodology

• Pipeline run: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=502082&view=results

[cwedgwood]

LGTM