Skip to content
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

Bug 1797647: [release-4.3] [baremetal] Ipv6 non virtual ip fix #1466

Merged

Conversation

russellb
Copy link
Member

This is a 4.3 backport of PRs #1436 and #1444

In IPv6 DHCPv6 environments, the prefix for the IPv6 address that we
must use to bind services may be 128. In case that happens, the current
detection code will fail to consider the address as being in the right
subnet.

Thankfully, thanks to the Route Advertisements, we get the prefix
information we need from the routing table. This patch adds the extra
code to generate pseudo CIDRs that allow us to check if an address is in
the right subnet.

Signed-off-by: Antoni Segura Puimedon <[email protected]>
This patch simplifies filtering by:
* Calling iface_cidrs only once,
* Filtering out IPv6 addresses marked with the *deprecated* flag
* Allowing multiple filters

Signed-off-by: Antoni Segura Puimedon <[email protected]>
This change prevents:
* Kubelet choosing as node IP an address from a non control plane subnet
  (like the provisioning network)
* Kubelet choosing a deprecated IPv6 address as its node IP that in
  several platform can be a VIP

Signed-off-by: Antoni Segura Puimedon <[email protected]>
CRI-O on startup could get addresses with expiring leases or from
interfaces that are in isolated networks. This patch extends
kubelet-nodeip.service to fix CRI-O as well.

Signed-off-by: Antoni Segura Puimedon <[email protected]>
@openshift-ci-robot
Copy link
Contributor

@russellb: This pull request references Bugzilla bug 1797647, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Bug 1797647: [release-4.3] [baremetal] Ipv6 non virtual ip fix

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.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 12, 2020
@openshift-ci-robot openshift-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Feb 12, 2020
@stevekuznetsov
Copy link

/retest

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 12, 2020
@sinnykumari
Copy link
Contributor

/test e2e-gcp-upgrade

@celebdor
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 13, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: celebdor, kikisdeliveryservice, russellb

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:
  • OWNERS [kikisdeliveryservice]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@mfojtik mfojtik added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 13, 2020
@openshift-merge-robot openshift-merge-robot merged commit f28509b into openshift:release-4.3 Feb 13, 2020
@runcom
Copy link
Member

runcom commented Mar 4, 2020

/bugzilla refresh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants