-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.14
-
No
-
False
-
-
Customer Escalated
Description of problem:
When adding a secondary network card(iSCSI traffic) to worker nodes during installation or with a machineSet, the newly deployed nodes fail to deploy and get hung in an initialized state: [map[effect:NoSchedule key:node.cloudprovider.kubernetes.io/uninitialized value:true]] Installing the cluster with only one network card works, but after trying to add the network card fails with the same result. Applying the same, during both installation and changing the machineSet in OpenShift 4.12 works without any issues.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Everytime in customer environment
Steps to Reproduce:
1. Install OCP 4.14 with a secondary network card (IPI) 2. Wait until worker are deployed 3. Workers never fully deploy or start
Actual results:
Workers not deploying or adding secondary NIC
Expected results:
Workers deplying with a secondary NIC
Additional info: