Bug 2211186

Summary:	[4.13] initial-job-dataimportcron pod ignores pod placement configuration
Product:	Container Native Virtualization (CNV)	Reporter:	Arnon Gilboa <agilboa>
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:	nashok, yadu
Target Milestone:	---
Target Release:	4.13.1
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	v4.13.1.rhel9-89	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2196429	Environment:
Last Closed:	2023-06-20 13:41:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arnon Gilboa 2023-05-30 16:18:34 UTC

+++ This bug was initially created as a clone of Bug #2196429 +++

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-08 08:01:08 UTC

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

initial-job-centos-stream8-image-cron-7e82fb69-nf5sk              0/1     ContainerCreating   0               0s      <none>         c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>
initial-job-centos-stream9-image-cron-01178bb3-l6jpt              0/1     ContainerCreating   0               0s      <none>         c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>
initial-job-centos-7-image-cron-07cda3d4-h84d6                    0/1     ContainerCreating   0               1s      <none>         c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>
initial-job-fedora-image-cron-4163f686-b742l                      0/1     ContainerCreating   0               1s      <none>         c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>
initial-job-centos-stream8-image-cron-7e82fb69-nf5sk              0/1     ContainerCreating   0               1s      <none>         c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>
initial-job-centos-stream9-image-cron-01178bb3-l6jpt              0/1     ContainerCreating   0               1s      <none>         c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>
initial-job-centos-7-image-cron-07cda3d4-h84d6                    1/1     Running             0               1s      10.129.3.145   c01-yadu413-57znv-worker-0-j9lrq   <none>           <none>

Comment 7 errata-xmlrpc 2023-06-20 13:41:05 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 (OpenShift Virtualization 4.13.1 Images), 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/RHEA-2023:3686