metal3-static-ip-set init container fails when there are two interfaces with same MAC and provisioningInterface is not set

[machacekondra]

metal3-static-ip-set init container fails when there are two interfaces with same MAC and provisioningInterface is not set

[metal3-io-bot]

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dtantsur]

Note: metal3-static-ip-set is specific to OpenShift, but I suspect the bug equally applies to upstream containers.

[Rozzii]

/triage needs-information

[dtantsur]

I think you're right that we don't handle a situation where two interfaces have the same MAC. How did you end up in this situation? What the behavior you'd expect? We need to know exactly 1 interface.

P.S.
Please avoid OpenShift-isms like metal3-static-ip-set and provisioning-configuration in upstream bugs. I know what you mean because I work on OpenShift, but some people do not. It could be beneficial for you to file a bug in the Red Hat Jira first, so that we can see how much it affects the upstream Metal3.