Bug 1768462 - [CNV-2.2 Deployment] virt-operator failing to pull container - manifest unknown for v2.2.0-2
Summary: [CNV-2.2 Deployment] virt-operator failing to pull container - manifest unkno...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Virtualization
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 2.2.0
Assignee: Simone Tiraboschi
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-04 14:03 UTC by Lukas Bednar
Modified: 2020-01-30 16:27 UTC (History)
7 users (show)

Fixed In Version: hco-bundle-registry:v2.2.0-7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-30 16:27:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:0307 0 None None None 2020-01-30 16:27:26 UTC

Description Lukas Bednar 2019-11-04 14:03:05 UTC
Description of problem:

openshift-cnv                                           virt-operator-795758f96f-fmjzt                                    0/1     ImagePullBackOff   0          18s
openshift-cnv                                           virt-operator-795758f96f-rbgbh                                    0/1     ImagePullBackOff   0          18s


Events:
  Type     Reason     Age                     From                       Message
  ----     ------     ----                    ----                       -------
  Normal   Scheduled  <unknown>               default-scheduler          Successfully assigned openshift-cnv/virt-operator-795758f96f-fmjzt to host-172-16-0-17
  Normal   Pulling    6m58s (x4 over 8m20s)   kubelet, host-172-16-0-17  Pulling image "registry-proxy.engineering.redhat.com/rh-osbs/virt-operator:v2.2.0-2"
  Warning  Failed     6m58s (x4 over 8m20s)   kubelet, host-172-16-0-17  Failed to pull image "registry-proxy.engineering.redhat.com/rh-osbs/virt-operator:v2.2.0-2": rpc error: code = Unknown desc = Error reading manifest v2.2.0-2 in registry-proxy.engineering.redhat.com/rh-osbs/virt-operator: manifest unknown: manifest unknown
  Warning  Failed     6m58s (x4 over 8m20s)   kubelet, host-172-16-0-17  Error: ErrImagePull
  Normal   BackOff    6m44s (x6 over 8m19s)   kubelet, host-172-16-0-17  Back-off pulling image "registry-proxy.engineering.redhat.com/rh-osbs/virt-operator:v2.2.0-2"
  Warning  Failed     3m12s (x21 over 8m19s)  kubelet, host-172-16-0-17  Error: ImagePullBackOff


Version-Release number of selected component (if applicable):
registry-proxy.engineering.redhat.com/rh-osbs/virt-operator:v2.2.0-2
OCP-4.3


Steps to Reproduce:
1. Deploy CNV-2.2 using qe-testing.sh script
2.
3.

Actual results: failing to pull images


Expected results: Successful deployment of CNV-2.2


Additional info:

Comment 1 Lukas Bednar 2019-11-04 14:18:10 UTC
My guess is that container name is missing `container-native-virtualization-`

Comment 2 Marc Sluiter 2019-11-04 14:18:53 UTC
Where is the qe-testing.sh skript coming from?

The image name is wrong, it needs the "container-native-virtualization-" prefix when pulling from registry-proxy.engineering.redhat.com/rh-osbs.

$ docker pull registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-virt-operator:v2.2.0-2
v2.2.0-2: Pulling from rh-osbs/container-native-virtualization-virt-operator
...
Digest: sha256:5a759d44ea4a9dca19df1bd10974dac8b50845fd69a0cb776411db6b0b20b295
Status: Downloaded newer image for registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-virt-operator:v2.2.0-2
registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-virt-operator:v2.2.0-2

Comment 4 Ryan Hallisey 2019-11-04 14:28:50 UTC
cc Simone, can you have a look?

Comment 5 Israel Pinto 2019-12-19 08:50:16 UTC
Verify:
Pull the right images:
registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-virt-operator:v2.2.0-10

Comment 7 errata-xmlrpc 2020-01-30 16:27: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, 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/RHEA-2020:0307


Note You need to log in before you can comment on or make changes to this bug.