Bug 2196429 - initial-job-dataimportcron pod ignores pod placement configuration
Summary: initial-job-dataimportcron pod ignores pod placement configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.12.2
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 4.14.0
Assignee: Arnon Gilboa
QA Contact: Yan Du
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-09 06:43 UTC by nijin ashok
Modified: 2023-11-08 14:06 UTC (History)
1 user (show)

Fixed In Version: v4.14.0.rhel9-811
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2211186 2211189 (view as bug list)
Environment:
Last Closed: 2023-11-08 14:05:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt containerized-data-importer pull 2712 0 None Merged Propagate CDI workload NodePlacement to DIC CronJob and initial Job 2023-05-30 08:05:28 UTC
Red Hat Issue Tracker CNV-28714 0 None None None 2023-05-09 07:01:50 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:06:11 UTC

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
Note You need to log in before you can comment on or make changes to this bug.