-
Notifications
You must be signed in to change notification settings - Fork 563
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
Panic Error: Invalid Memory Address or Nil Pointer Dereference during Taint Deletion in AWSManagedMachinePool #5021
Comments
This issue is currently awaiting triage. If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the The 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-sigs/prow repository. |
This commit addresses a panic error that occurs when attempting to delete a taint in AWSManagedMachinePool. The issue was caused by a nil pointer dereference when the taint's value was nil. By handling nil values for taint fields, this fix ensures that taints with nil values are correctly processed, preventing runtime errors. Fixes [kubernetes-sigs#5021](kubernetes-sigs#5021) Signed-off-by: nueavv <nuguni@kakao.com>
This commit addresses a panic error that occurs when attempting to delete a taint in AWSManagedMachinePool. The issue was caused by a nil pointer dereference when the taint's value was nil. By handling nil values for taint fields, this fix ensures that taints with nil values are correctly processed, preventing runtime errors. Fixes [kubernetes-sigs#5021](kubernetes-sigs#5021) Signed-off-by: nueavv <nuguni@kakao.com>
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
This commit addresses a panic error that occurs when attempting to delete a taint in AWSManagedMachinePool. The issue was caused by a nil pointer dereference when the taint's value was nil. By handling nil values for taint fields, this fix ensures that taints with nil values are correctly processed, preventing runtime errors. Fixes [kubernetes-sigs#5021](kubernetes-sigs#5021) Signed-off-by: nueavv <nuguni@kakao.com>
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/kind bug
What steps did you take and what happened:
While managing an EKS cluster using AWSManagedMachinePool, a panic error occurs when trying to delete a taint after adding it. Below are the related log messages.
Initial Error Log
Updated Error Log
What did you expect to happen:
Taints should be deleted without causing a panic error.
Anything else you would like to add:
Current
TaintsFromSDK
function implementation:Suggestions:
Resolve the panic error that occurs during taint deletion.
When the taint array is empty, ensure that existing taints are deleted.
Review the logic handling empty taint arrays and nil fields.
Environment:
Cluster-api-provider-aws version: [version] 2.5.0
Kubernetes version: (use kubectl version): [version] 1.25.5 on local kubernetes
OS (e.g. from /etc/os-release): [version] ubuntu 20.04
The text was updated successfully, but these errors were encountered: