Bug 1800979

Summary: Update adding Windows guest tools CD to point to new virtio-win image
Product: Container Native Virtualization (CNV) Reporter: Radim Hrazdil <rhrazdil>
Component: DocumentationAssignee: Andrew Burden <aburden>
Status: CLOSED CURRENTRELEASE QA Contact: Irina Gulina <igulina>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.2.0CC: aburden, cnv-qe-bugs, ipinto, kbidarka, ncredi
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-02-14 15:20:59 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 Radim Hrazdil 2020-02-09 18:01:20 UTC
Document URL: 

Documentation should point users adding guest tools image to 
https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/virtio-win instead of cnv-tech-preview/virtio-win.

See BZ1800488 for more info.

Comment 1 Andrew Burden 2020-02-11 12:05:31 UTC
The container name and url have been updated:

PR: 
https://github.com/openshift/openshift-docs/pull/19654

Rendered build:
https://cnv-bz1800979-virtio-url--ocpdocs.netlify.com/openshift-enterprise/latest/cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-existing-windows-vm.html
https://cnv-bz1800979-virtio-url--ocpdocs.netlify.com/openshift-enterprise/latest/cnv/cnv_virtual_machines/cnv-installing-virtio-drivers-on-new-windows-vm.html

Radim, the CNV 2.1 are still on the portal, should they also be updated?
And will this need to be updated again for 2.3, or can we expect the name/url to persist?

Comment 2 Radim Hrazdil 2020-02-11 14:30:41 UTC
Hello Andrew,

I believe there will be no change for CNV 2.3. WRT CNV 2.1, I'm not sure, @Nelly, what do you think?

Comment 3 Nelly Credi 2020-02-11 17:54:39 UTC
@Israel, what say you?

Comment 5 Kedar Bidarkar 2020-02-12 11:30:41 UTC
So looked at RedHat Ecosystem catalog, 

For RH OCP - 3.x based CNV-1.4 the container image to pull is registry.redhat.io/cnv-tech-preview/virtio-win:v1.4.x

For all RH OCP - 4.x  the container image to pull appears to be is registry.redhat.io/container-native-virtualization/virtio-win:v2.x


I tested both of them,

 using my Red Hat Customer portal credentials  and was able to download successfully.

[kbidarka@kbidarka-host imagestreamtags]$ podman pull registry.redhat.io/container-native-virtualization/virtio-win
Trying to pull registry.redhat.io/container-native-virtualization/virtio-win...
Getting image source signatures
Copying blob ded517d07e66 done  
Copying blob 5e98065763a5 done  
Copying blob 645c2831c08a done  
Copying config eec8a55294 done  
Writing manifest to image destination
Storing signatures
eec8a55294c8a204b75003a9e46517ec5448f9e31cc5ef2dd81799595f8a11de


[kbidarka@kbidarka-host imagestreamtags]$ podman pull registry.redhat.io/cnv-tech-preview/virtio-win
Trying to pull registry.redhat.io/cnv-tech-preview/virtio-win...
Getting image source signatures
Copying blob 4c98734f2433 done  
Copying blob 17942523bc4b done  
Copying blob 6091b3ef3add done  
Copying config 718db070c3 done  
Writing manifest to image destination
Storing signatures
718db070c305745ae2756a0d338b9677c23eddab1a1f9b807693ca889a36a60b



Feel if updating docs for 4.2/cnv-2.1 is possible, we probably should update those as well, 
that is from cnv-tech-preview/virtio-win to container-native-virtualization/virtio-win .


In short for CNV-2.x which is based on RH OCP4.x , the container image "virtio-win" should all point to container-native-virtualization/virtio-win.

Comment 6 Irina Gulina 2020-02-12 16:13:03 UTC
@Andrew, PR looks good. Please merge. Thanks