Bug 2051968

Summary: virt-freezer binary missing from downstream virt-launcher
Product: Container Native Virtualization (CNV) Reporter: Alex Kalenyuk <akalenyu>
Component: StorageAssignee: Alex Kalenyuk <akalenyu>
Status: CLOSED ERRATA QA Contact: dalia <dafrank>
Severity: high Docs Contact:
Priority: high    
Version: 4.10.0CC: alitke, cnv-qe-bugs, ngavrilo, pelauter
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-launcher v4.10.0-211, CNV v4.10.0-663 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-16 16:07:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alex Kalenyuk 2022-02-08 12:48:47 UTC 
Description of problem:
virt-freezer binary does not exist in downstream virt-launcher container
making it impossible to use the kubevirt Velero plugin

Version-Release number of selected component (if applicable):
CNV 4.10.0

How reproducible:
100%

Steps to Reproduce:
1. Create VM, check for virt-freezer binary in virt-launcher pod

Actual results:
/usr/bin/virt-freezer: no such file or directory

Expected results:
virt-freezer exists

Additional info:
virt-freezer job is to freeze/unfreeze the VM from within the launcher pod (without going through the KubeVirt API) for the sake of Velero backup hooks
Comment 1 Adam Litke 2022-02-08 13:01:49 UTC 
Peter, here's another one.  Without this, the velero plugin cannot work properly.
Comment 2 dalia 2022-02-13 13:21:53 UTC 
verified on CNV 4.10
Comment 5 errata-xmlrpc 2022-03-16 16:07:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Virtualization 4.10.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0947