Bug 2196429

Summary:	initial-job-dataimportcron pod ignores pod placement configuration
Product:	Container Native Virtualization (CNV)	Reporter:	nijin ashok <nashok>
Component:	Storage	Assignee:	Arnon Gilboa <agilboa>
Status:	CLOSED ERRATA	QA Contact:	Yan Du <yadu>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.12.2	CC:	yadu
Target Milestone:	---
Target Release:	4.14.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	v4.14.0.rhel9-811	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2211186 2211189 (view as bug list)		Environment:
Last Closed:	2023-11-08 14:05:46 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 nijin ashok 2023-05-09 06:43:01 UTC

Add tolerations in node placement rules as per https://docs.openshift.com/container-platform/4.12/virt/install/virt-specifying-nodes-for-virtualization-components.html.

These rules are not getting propagated to the initial-job-dataimportcron pod. 

When all nodes have taints set, these pod will be stuck in "Pending" status.

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

OpenShift Virtualization 4.12.2

How reproducible:

100%

Steps to Reproduce:

1. Add node placement rules on hco object.
2. Check the placement rules are applied to  pod.

Actual results:

kubevirt-job pod ignores node placement configuration

Expected results:

Node placement configuration should be propagated to initial-job-dataimportcron pod.

Additional info:

Comment 1 Yan Du 2023-06-09 07:38:16 UTC

Test on CNV-v4.14.0.rhel9-825, init jobs only are scheduled to the specific node as the nodePlacement rules.

initial-job-centos-stream9-image-cron-3178f8e6-fjsrz              0/1     ContainerCreating   0             0s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-fedora-image-cron-d5189342-ntl58                      0/1     Pending             0             0s      <none>          <none>                             <none>           <none>
initial-job-fedora-image-cron-d5189342-ntl58                      0/1     Pending             0             0s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-fedora-image-cron-d5189342-ntl58                      0/1     Pending             0             0s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-fedora-image-cron-d5189342-ntl58                      0/1     ContainerCreating   0             0s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-centos-7-image-cron-4af0342f-bnprd                    0/1     ContainerCreating   0             1s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-centos-stream9-image-cron-3178f8e6-fjsrz              0/1     ContainerCreating   0             1s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-centos-stream8-image-cron-a90eb314-lkl85              0/1     ContainerCreating   0             1s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>
initial-job-fedora-image-cron-d5189342-ntl58                      0/1     ContainerCreating   0             1s      <none>          c01-yadu414-cwlzs-worker-0-j45h5   <none>           <none>

Comment 3 errata-xmlrpc 2023-11-08 14:05:46 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 (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), 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-2023:6817