Bug 1800488
| Summary: | Windows guest tool container image added with VM Detail page Modal is incorrect in d/s | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Radim Hrazdil <rhrazdil> |
| Component: | Console Kubevirt Plugin | Assignee: | Radim Hrazdil <rhrazdil> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Radim Hrazdil <rhrazdil> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aburden, aos-bugs, danken, gouyang, pkotas |
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-20 11:16:19 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: | |||
I believe that both docs and code should point to https://access.redhat.com/containers/#/registry.access.redhat.com/container-native-virtualization/virtio-win With the help of Radim, we figured the issue. Red Hat Enterprise Linux CoreOS release 4.3 is based on RHEL 7, therefore it has the registries configured as: ``` # This is a system-wide configuration file used to # keep track of registries for various container backends. # It adheres to TOML format and does not support recursive # lists of registries. # The default location for this configuration file is /etc/containers/registries.conf. # The only valid categories are: 'registries.search', 'registries.insecure', # and 'registries.block'. [registries.search] registries = ['registry.access.redhat.com', 'docker.io'] ``` The image is stored at registry.redhat.io which is present by default on RHEL 8 based hosts. The simplest solution is to provide full path to the image as generated in the UI. Another possible solution is to add the registry to the host, which is an unnecessary complication that can cause possible issues. Docs PR posted in related bug: BZ#1800979 Petr, the prerequisite for both procedures says: "Download the cnv-tech-preview/virtio-win container disk from the Red Hat Container Catalog. This is not mandatory, because the container disk will be downloaded from the Red Hat registry if it not already present in the cluster, but it can reduce installation time." Does your previous comment mean the second sentence is incorrect, and that it won't be downloaded because the registry is not present on the host? As far as I understood the issue. The bug applies only on CoreOS host. For full RHEL it should be fine. Although I need to check further what is the target registry. The image is "registry.redhat.io/container-native-virtualization/virtio-win" and it's can be pulled "Successfully pulled image "registry.redhat.io/container-native-virtualization/virtio-win"". Verified on 4.4.0-0.nightly-2020-02-22-102956 |
Description of problem: According to a CNV documentation, the windows gest tools containerdisk should look like the following: - containerDisk: image: cnv-tech-preview/virtio-win name: windows-guest-tools However, the UI Modal window adds the following: - containerDisk: image: virtio-win-container name: windows-guest-tools Which leads to Failed to pull image "virtio-win-container": rpc error: code = Unknown desc = Error reading manifest latest in docker.io/library/virtio-win-container: errors: denied: requested access to the resource is denied unauthorized: authentication required Version-Release number of selected component (if applicable): OCP 4.3 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: