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

kubeadm: fix the bug that windows node failed to join IPv6 cluster due to preflight failures #108769

Merged
merged 1 commit into from
Mar 17, 2022

Conversation

SataQiu
Copy link
Member

@SataQiu SataQiu commented Mar 17, 2022

What type of PR is this?

/kind bug

What this PR does / why we need it:

kubeadm: fix the bug that windows node failed to join IPv6 cluster due to preflight failures

Which issue(s) this PR fixes:

Fixes kubernetes/kubeadm#2664

Special notes for your reviewer:

Does this PR introduce a user-facing change?

kubeadm: fix a bug where Windows nodes fail to join an IPv6 cluster due to preflight errors

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

…e to preflight failures

Signed-off-by: SataQiu <shidaqiu2018@gmail.com>
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. kind/bug Categorizes issue or PR as related to a bug. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. release-note Denotes a PR that will be considered when it comes time to generate release notes. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. approved Indicates a PR has been approved by an approver from all required OWNERS files. area/kubeadm and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Mar 17, 2022
@aojea
Copy link
Member

aojea commented Mar 17, 2022

it seems you have per OS files

find cmd/kubeadm/app/preflight/
cmd/kubeadm/app/preflight/
cmd/kubeadm/app/preflight/utils.go
cmd/kubeadm/app/preflight/utils_test.go
cmd/kubeadm/app/preflight/checks.go
cmd/kubeadm/app/preflight/checks_darwin.go
cmd/kubeadm/app/preflight/checks_linux.go
cmd/kubeadm/app/preflight/checks_test.go
cmd/kubeadm/app/preflight/checks_unix.go
cmd/kubeadm/app/preflight/checks_windows.go

@neolit123
Copy link
Member

i verified that all of these are now branched with goos == linux:

 	bridgenf                    = "/proc/sys/net/bridge/bridge-nf-call-iptables"
	bridgenf6                   = "/proc/sys/net/bridge/bridge-nf-call-ip6tables"
	ipv4Forward                 = "/proc/sys/net/ipv4/ip_forward"
	ipv6DefaultForwarding       = "/proc/sys/net/ipv6/conf/default/forwarding"

thanks for the PR
/lgtm
/approve
/triage accepted
/priority backlog

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Mar 17, 2022
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 17, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neolit123, SataQiu

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@neolit123
Copy link
Member

neolit123 commented Mar 17, 2022

it seems you have per OS files

having OS-specific logic in the OS files is definitely better.
there are already a few OS runtime branches in the code, so maybe we can do it in a separate refactor.
it will likely be quite messy...

@neolit123
Copy link
Member

/retest

@neolit123
Copy link
Member

/release-note-edit

kubeadm: fix a bug where Windows nodes fail to join an IPv6 cluster due to preflight errors

(just a minor edit)

@neolit123
Copy link
Member

/sig cluster-lifecycle
bot labels seem flaky lately.

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 17, 2022
@k8s-ci-robot k8s-ci-robot merged commit 4d08582 into kubernetes:master Mar 17, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.24 milestone Mar 17, 2022
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. area/kubeadm cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/backlog Higher priority than priority/awaiting-more-evidence. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows Node fails to join IPv6 cluster
4 participants