Bug 1879994

Summary: v2v-conversion-image is not updated during CNV upgrade from 2.4.0 to 2.4.1
Product: Container Native Virtualization (CNV) Reporter: Fabien Dupont <fdupont>
Component: V2VAssignee: Brett Thurber <bthurber>
Status: CLOSED DUPLICATE QA Contact: Daniel Gur <dagur>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.4.1CC: aos-bugs, cnv-qe-bugs, fdupont, fkrepins, rjones, tgolembi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-22 18:40:06 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 Fabien Dupont 2020-09-17 14:06:26 UTC 
Description of problem:

When upgrading CNV from 2.4.0 to 2.4.1, the "v2v-conversion-image" attribute of the "v2v-vmware" config map is not updated with the SHA256 signature of the image for 2.4.1. The consequence is that the import will still use the 2.4.0 image.


To find what the SHA256 signature of an image is, one can use the following commands:

$ podman login registry.redhat.io
$ podman pull registry.redhat.io/container-native-virtualization/kubevirt-v2v-conversion:v2.4.0
$ podman inspect registry.redhat.io/container-native-virtualization/kubevirt-v2v-conversion:v2.4.0 | jq '.[]["Digest"]'

The SHA256 in "v2v-conversion-image" was "e3056e80f0aecf186bfac6504f23aa58d33120d0ba9646a816bd4f341b030cae", while should have been "f160e205506908b7145a1414158721c9c01ffdcf12f55ebe38d8f22432a92d08".


Version-Release number of selected component: 2.4.0 and 2.4.1
Comment 1 Filip Krepinsky 2020-09-21 08:42:49 UTC 
this should be handled by upgrade of HCO and not CNV. Also the UI just reads the value from config map and does not manage it. Moving..
Comment 3 Brett Thurber 2020-09-22 18:40:06 UTC 

*** This bug has been marked as a duplicate of bug 1879993 ***