Bug 1838424

Summary: [Installation] CNV 2.4.0 virt-handler and kubevirt-node-labeller pods are not showing up
Product: Container Native Virtualization (CNV) Reporter: Satyajit Bulage <sbulage>
Component: InstallationAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED ERRATA QA Contact: Tareq Alayan <talayan>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 2.4.0CC: cnv-qe-bugs, ksimon, ncredi, sgott, stirabos
Target Milestone: ---Keywords: Regression, TestBlocker
Target Release: 2.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hco-bundle-registry-container-v2.3.0-271 hyperconverged-cluster-operator-container-v2.3.0-62 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-28 19:10:07 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 Satyajit Bulage 2020-05-21 06:39:25 UTC 
Description of problem:


Version-Release number of selected component (if applicable):CNV 2.4.0


How reproducible:100%


Steps to Reproduce:
1. Install CNV 2.4 operator
2.
3.

Actual results: virt-handler pod showing Init:CrashLoopBackOff and kubevirt-node-labeller pods are in pending state.


Expected results:All pods should be in up and running state.


Additional info:
output of oc get pods -nopenshift-cnv :

kubevirt-node-labeller-7nd2n                       0/1     Pending                 0          5h16m
kubevirt-node-labeller-d6rpf                       0/1     Pending                 0          5h16m
kubevirt-node-labeller-gbmqv                       0/1     Pending                 0          5h16m
virt-handler-2pr74                                 0/1     Init:CrashLoopBackOff   66         5h16m
virt-handler-cwh2m                                 0/1     Init:CrashLoopBackOff   66         5h16m
virt-handler-l98ww                                 0/1     Init:CrashLoopBackOff   66         5h16m
Comment 1 Simone Tiraboschi 2020-05-21 10:48:56 UTC 
This is also a side effect of https://github.com/kubevirt/kubevirt/pull/3133
that moved node-labeller and cpu plugin from ssp operator into kubevirt one.
Comment 2 Karel Šimon 2020-05-21 11:57:31 UTC 
Satyajit can you please post logs from virt-handler?
Comment 4 Satyajit Bulage 2020-06-02 09:39:26 UTC 
I have managed to deploy CNV 2.4 (latest) and found that after installation all pods are in running state.
Verifying this BZ.
Comment 7 errata-xmlrpc 2020-07-28 19:10:07 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/RHSA-2020:3194