Description of problem (please be detailed as possible and provide log snippests): when creating NAD, you need to define the NIC name for each NAD, and if you have different type of hosts workers / masters , the NIC names can be different. since in the NAD you can define only one NIC name, the cluster can not deploy and the mons are stuck in Init state. Version of all relevant components (if applicable): OCP : 4.8.0 OCS : 4.8.0-450.ci Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? i can not run with multus Is there any workaround available to the best of your knowledge? not that i aware of. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? yes Can this issue reproduce from the UI? the cluster deployed from UI If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. deploy OCP on BM environment - Masters and workers are from different HW type. 2. deploy OCS (without a cluster) 3. create NAD 3. try to deploy the cluster from UI, and select Multus as networking Actual results: the installation is stuck on Init state of the MON's Expected results: The cluster will deploy Additional info:
Not a blocker for 4.8, it's a feature request. We could mitigate with udev rule on machine config to always get the same name, but this is not on ODF. Potentially ODF could accept one more NAD for workers only. Which will leave NADs for cluster side and workers. Moving to 4.9.
Moving to 4.10, needs more feature design.
Reading this again, we believe it could lead to potential confusion to separate hosts workers/masters configurations. Hopefully most of the time the NIC name will be homogenous regardless of the type of node. Also, this is addressing a particular case where the mons run on the master nodes, which is not a common configuration. If NICs are different we should really look into the direction of adding a machine config with an udev rule to rename the NIC so that it is identical on all the nodes.