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

Fix install_cni_chaining not creating CNI conf correctly in some cases #6506

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

tnqn
Copy link
Member

@tnqn tnqn commented Jul 5, 2024

The chaining CNI conf was not created correctly under two conditions:

  1. If there is non CNI conf file in the directory, like a kubeconfig required by the primary CNI.
  2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be written before using it to create the chaining CNI conf.

Fixes #6499

The chaining CNI conf was not created correctly under two conditions:

1. If there is non CNI conf file in the directory, like a kubeconfig
   required by the primary CNI.
2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be
written before using it to create the chaining CNI conf.

Signed-off-by: Quan Tian <quan.tian@broadcom.com>
@tnqn tnqn added action/backport Indicates a PR that requires backports. action/release-note Indicates a PR that should be included in release notes. labels Jul 5, 2024
@tnqn
Copy link
Member Author

tnqn commented Jul 5, 2024

cc @tnn-simon

@tnqn tnqn added this to the Antrea v2.1 release milestone Jul 5, 2024
@tnn-simon
Copy link

LGTM. I have not managed to reproduce the bug after applying this fix.

@tnqn
Copy link
Member Author

tnqn commented Jul 5, 2024

LGTM. I have not managed to reproduce the bug after applying this fix.

@tnn-simon thanks for reviewing and testing.

@tnqn
Copy link
Member Author

tnqn commented Jul 8, 2024

/skip-all

@tnqn tnqn merged commit 68ab657 into antrea-io:main Jul 8, 2024
53 of 59 checks passed
@tnqn tnqn deleted the fix-install-cni-chaining branch July 8, 2024 03:04
tnqn added a commit to tnqn/antrea that referenced this pull request Jul 8, 2024
antrea-io#6506)

The chaining CNI conf was not created correctly under two conditions:

1. If there is non CNI conf file in the directory, like a kubeconfig
   required by the primary CNI.
2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be
written before using it to create the chaining CNI conf.

Signed-off-by: Quan Tian <quan.tian@broadcom.com>
tnqn added a commit to tnqn/antrea that referenced this pull request Jul 8, 2024
antrea-io#6506)

The chaining CNI conf was not created correctly under two conditions:

1. If there is non CNI conf file in the directory, like a kubeconfig
   required by the primary CNI.
2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be
written before using it to create the chaining CNI conf.

Signed-off-by: Quan Tian <quan.tian@broadcom.com>
tnqn added a commit to tnqn/antrea that referenced this pull request Jul 8, 2024
antrea-io#6506)

The chaining CNI conf was not created correctly under two conditions:

1. If there is non CNI conf file in the directory, like a kubeconfig
   required by the primary CNI.
2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be
written before using it to create the chaining CNI conf.

Signed-off-by: Quan Tian <quan.tian@broadcom.com>
tnqn added a commit that referenced this pull request Jul 9, 2024
#6506) (#6510)

The chaining CNI conf was not created correctly under two conditions:

1. If there is non CNI conf file in the directory, like a kubeconfig
   required by the primary CNI.
2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be
written before using it to create the chaining CNI conf.

Signed-off-by: Quan Tian <quan.tian@broadcom.com>
tnqn added a commit that referenced this pull request Jul 9, 2024
#6506) (#6509)

The chaining CNI conf was not created correctly under two conditions:

1. If there is non CNI conf file in the directory, like a kubeconfig
   required by the primary CNI.
2. If the CNI conf file is created but not completely written yet.

The patch ensures it only selects valid CNI conf and waits for it to be
written before using it to create the chaining CNI conf.

Signed-off-by: Quan Tian <quan.tian@broadcom.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action/backport Indicates a PR that requires backports. action/release-note Indicates a PR that should be included in release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CNI chaining fails and does not self-heal in AKS
3 participants