Open machacekondra opened 1 month ago
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.
Note: metal3-static-ip-set
is specific to OpenShift, but I suspect the bug equally applies to upstream containers.
/triage needs-information
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.
When
metal3-static-ip-set
init container is executed on env where there two interface with same MAC address following script: metal3-static-ip-set init containerfails, as it returns both interfaces delimited by new line and so the init container fails, because later such interface name don't exist. Here is example of failed script execution:
As you can see it tries to find interface:
Workaround is edit
provisioning
resourceprovisioning-configuration
with following configuration:Is there a way to specify such configuration in openshift install config?