-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
False
-
-
False
-
NoActiveCustomerTickets
-
CLOSED
-
---
-
---
-
-
-
Storage Core Sprint 237
-
High
-
No
+++ 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: