Bug 2224552

Summary: Virt-template-validator pods are getting scheduled on same node on Upgraded cluster
Product: Container Native Virtualization (CNV) Reporter: Akriti Gupta <akrgupta>
Component: SSPAssignee: Dominik Holler <dholler>
Status: NEW --- QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.11.5CC: dshchedr
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: 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 Akriti Gupta 2023-07-21 12:35:43 UTC 
Description of problem: 
virt-template-validator pods are getting scheduled on same nodes on a upgraded cluster 
On Fresh install pods are on different nodes
probably because of node drain during CNV upgrade pods are scheduling on same nodes

[akriti@fedora ~]$ oc describe pod virt-template-validator-6d8c4bbf5b-t27pw -n openshift-cnv | grep Node:
Node:                 cnv-qe-infra-07.cnvqe2.lab.eng.rdu2.redhat.com/10.1.156.7
[akriti@fedora ~]$ oc describe pod virt-template-validator-6d8c4bbf5b-w829z -n openshift-cnv | grep Node:
Node:                 cnv-qe-infra-07.cnvqe2.lab.eng.rdu2.redhat.com/10.1.156.7

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


How reproducible:


Steps to Reproduce:
1. oc describe pod <virt-template-validator pod1>
2. oc describe pod <virt-template-validator pod2>
3.

Actual results:
both scheduled on same node

Expected results:
both scheduled on different nodes

Additional info:
Earlier we had a sililar bug fixed for fressh install
https://bugzilla.redhat.com/show_bug.cgi?id=2056467