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] Add new subnet will get "invalid memory address or nil pointer dereference" err #4493

Closed
Longchuanzheng opened this issue Sep 9, 2024 · 2 comments · Fixed by #4494
Closed
Labels
bug Something isn't working subnet

Comments

@Longchuanzheng
Copy link
Contributor

Kube-OVN Version

v1.12.22

Kubernetes Version

1.25.1

Operation-system/Kernel Version

4.19

Description

When add new subnet, it will return panic: runtime error: invalid memory address or nil pointer dereference
image

Steps To Reproduce

update kube-ovn to v1.12.22

Current Behavior

kube-ovn-controller CrashLoopBackOff

Expected Behavior

kube-ovn-controller running

@Longchuanzheng Longchuanzheng added the bug Something isn't working label Sep 9, 2024
@dosubot dosubot bot added the subnet label Sep 9, 2024
Copy link

dosubot bot commented Sep 9, 2024

Hey @Longchuanzheng! 👋 I'm here to help you with any bugs, questions, or contributions. Let's get this sorted out together!

I found some similar issues that might be relevant to your problem:

  1. "controller panic runtime error: invalid memory address or nil pointer dereference(在1.12.4版本复现)" - This issue was closed and referenced by a fix for a nil pointer [1].
  2. "invalid memory address or nil pointer dereference" in vpc_nat.go - This issue was also closed and referenced by a fix for an invalid memory address [2].

To resolve the "invalid memory address or nil pointer dereference" error when adding a new subnet in Kube-OVN v1.12.22 on Kubernetes v1.25.1, you should update to Kube-OVN v1.12.20 or later. The changelog for Kube-OVN v1.12.20 includes a fix for a nil pointer issue:

* [b2f7da5f](https://github.com/kubeovn/kube-ovn/commit/b2f7da5fc24bb50ae3358e05c065b35eda9c5e54) fix nil pointer (#3661)

This fix should address the error you are encountering [3].

To continue talking to Dosu, mention @dosu.

@bobz965
Copy link
Collaborator

bobz965 commented Sep 9, 2024

校验 以 /32 结尾的非法 ipv4 cidr,同理校验 /128 结尾的非法 ipv6 cidr,目前会导致空指针问题。

init ipam 需要补充log,表明处理哪个子网,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working subnet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants