Bug 2066223 - [CNV-4.11-HCO] openshift-virtualization-os-images NS ReconcileFailed
Summary: [CNV-4.11-HCO] openshift-virtualization-os-images NS ReconcileFailed
Keywords:
Status: CLOSED DUPLICATE of bug 2063540
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: SSP
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dominik Holler
QA Contact: Geetika Kapoor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-21 09:46 UTC by Mor Cohen
Modified: 2022-03-21 14:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-21 14:20:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mor Cohen 2022-03-21 09:46:32 UTC
Description of problem:
When trying to install CNV-4.11, HCO reconciliation is failing.

    conditions:
    - lastTransitionTime: "2022-03-19T04:15:23Z"
      message: 'Error while reconciling: namespaces "openshift-virtualization-os-images"
        not found'
      observedGeneration: 2
      reason: ReconcileFailed
      status: "False"
      type: ReconcileComplete

Probably because kubevirt-os-images ns is created while openshift-virtualization-os-images ns is not.


Version-Release number of selected component (if applicable):
IIB-198659
hco-bundle-registry-container-v4.11.0-136

How reproducible:
100

Steps to Reproduce:
1. Install the mentioned above build of CNV.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Andrej Krejcir 2022-03-21 12:16:26 UTC
This will be probably fixed by the same patch that fixed BZ 2063540.

Comment 2 Simone Tiraboschi 2022-03-21 13:23:53 UTC
Moving to SSP component as it's quite related to https://bugzilla.redhat.com/show_bug.cgi?id=2063540
Feel free to close as a duplicate of that one.

Comment 3 Andrej Krejcir 2022-03-21 14:20:23 UTC

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


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