Handle dual-stack configuration in inspection data#758
Handle dual-stack configuration in inspection data#758metal3-io-bot merged 2 commits intometal3-io:masterfrom
Conversation
|
/test-integration |
|
Tested in a dual-stack environment and this does work as expected: |
|
/test-integration |
|
This version looks good. /approve |
Currently we assume only an ipv4 *or* an ipv6 IP exists in the inspection data, but it's valid for both to exist in a dual-stack scenario. To avoid changing the BMH API, in this case we create an additional nic entry in the list, which will contain each IP but otherwise the same data. Fixes: metal3-io#458
Thanks - I just pushed a minor update to the test (I forgot to compare the value for the NoIp nic added in the previous revision) |
bfournie
left a comment
There was a problem hiding this comment.
Do you think description here needs to change to indicate a 2nd nic will be used for dual-stack? https://github.com/metal3-io/baremetal-operator/blob/master/config/crd/bases/metal3.io_baremetalhosts.yaml#L343
Good point, thanks! I'll push another commit which clarifies that. |
|
/test-integration |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bfournie, dhellmann, hardys The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |
Currently we assume only an ipv4 or an ipv6 IP exists in the
inspection data, but it's valid for both to exist in a dual-stack
scenario.
To avoid changing the BMH API, in this case we create an additional
nic entry in the list, which will contain each IP but otherwise
the same data.
Fixes: #458