This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2224552 - Virt-template-validator pods are getting scheduled on same node on Upgraded cluster
Summary: Virt-template-validator pods are getting scheduled on same node on Upgraded ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: SSP
Version: 4.11.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: future
Assignee: Dominik Holler
QA Contact: Geetika Kapoor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-21 12:35 UTC by Akriti Gupta
Modified: 2023-12-14 16:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-14 16:05:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   CNV-31225 0 None None None 2023-12-14 16:05:25 UTC

Internal Links: 2232320

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
Comment 3 Dominik Holler 2023-08-30 14:36:06 UTC 
targeting to future for now, let's see if the behavior is reproducible if the scheduler has a chance to avoid it.
Comment 4 Akriti Gupta 2023-09-01 08:17:30 UTC 
currently this issue is more visible on a compact cluster
Note You need to log in before you can comment on or make changes to this bug.