-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Bug 1972524: baremetal: Ensure ipv6 bootstrap VM client-id is predictable #5110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
In openshift#4052 we added interfaces to control the MAC addresses for the NICs in the bootstrap VM, so that in environments where DHCP pools are not allowed, a static reservation can be made. Unfortunately that doesn't work in ipv6 environments currently, because NetworkManager needs a specific configuration similar to that applied via the MCO[1] for cluster hosts to ensure the generated client-ID is derived from the MAC and predictable. [1] https://github.com/openshift/machine-config-operator/blob/master/templates/common/on-prem/files/NetworkManager-onprem.conf.yaml
@hardys: This pull request references Bugzilla bug 1972524, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request. In response to this:
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. |
I tested this and we can now see if you set e.g
|
/label platform/baremetal |
These control the MAC for the bootstrap VM NICs, not the bridges on the host where the VM is running.
Note we should ensure e2e-metal-ipi-ovn-ipv6 passes before merging this |
/test e2e-metal-ipi-ovn-ipv6 |
2 similar comments
/test e2e-metal-ipi-ovn-ipv6 |
/test e2e-metal-ipi-ovn-ipv6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/test e2e-metal-ipi-ovn-ipv6 |
/approve Feel free to release the hold when metal IPv6 passes |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kirankt, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-metal-ipi-ovn-ipv6 |
Looks like we hit an issue which will be fixed via openshift/cluster-kube-apiserver-operator#1202 - probably best to hold off retesting until that lands |
/retest |
/test e2e-metal-ipi-ovn-ipv6 |
1 similar comment
/test e2e-metal-ipi-ovn-ipv6 |
@hardys: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
/retest-required |
/hold cancel |
@hardys: All pull requests linked via external trackers have merged: Bugzilla bug 1972524 has been moved to the MODIFIED state. In response to this:
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. |
/cherry-pick release-4.8 |
@hardys: new pull request created: #5250 In response to this:
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. |
In openshift#5110 we hade sure that for Baremetal IPI the IPv6 bootstrap VM client-id is predictable. This however did not cover UPI deployments. With this change deployments with platform `none` will also use predictable client-id. Fixes: OCPBUGS-33496
In #4052 we added interfaces to control the MAC addresses for the
NICs in the bootstrap VM, so that in environments where DHCP pools
are not allowed, a static reservation can be made.
Unfortunately that doesn't work in ipv6 environments currently,
because NetworkManager needs a specific configuration similar to
that applied via the MCO[1] for cluster hosts to ensure the
generated client-ID is derived from the MAC and predictable.
[1] https://github.com/openshift/machine-config-operator/blob/master/templates/common/on-prem/files/NetworkManager-onprem.conf.yaml