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.

Sign up for GitHub

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

Jump to bottom

CEL: Invalid value: "object": internal error: runtime error: index out of range [3] with length 3 evaluating rule: <rule name> #114661

Closed
inteon opened this issue Dec 22, 2022 · 10 comments · Fixed by #114857
Closed

CEL: Invalid value: "object": internal error: runtime error: index out of range [3] with length 3 evaluating rule: <rule name> #114661

inteon opened this issue Dec 22, 2022 · 10 comments · Fixed by #114857
Assignees
@jpbetz @cici37
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@inteon
Copy link
Member

inteon commented Dec 22, 2022 •
edited

What happened?

I'm seeing this error when posting an update to the kubernetes API:
Invalid value: "object": internal error: runtime error: index out of range [3] with length 3 evaluating rule: <rule name>

What did you expect to happen?

No error

How can we reproduce it (as minimally and precisely as possible)?

https://github.com/inteon/CEL_bug

Anything else we need to know?

No response

Kubernetes version

$ ./kube-apiserver --version
Kubernetes v1.25.0

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)
@inteon inteon added the kind/bug Categorizes issue or PR as related to a bug. label Dec 22, 2022
@k8s-ci-robot k8s-ci-robot added 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. labels Dec 22, 2022
@inteon
Copy link
Member Author

inteon commented Dec 22, 2022

/sig api-machinery

@k8s-ci-robot k8s-ci-robot added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 22, 2022
@liggitt
Copy link
Member

liggitt commented Dec 22, 2022

/cc @cici37 @jpbetz

@liggitt
Copy link
Member

liggitt commented Dec 22, 2022

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Dec 22, 2022
@cici37
Copy link
Contributor

cici37 commented Dec 22, 2022

Hi @inteon Thanks for raising the issue.
I have tested with the CRD from your repo here and it is working fine with my 1.26 cluster. Would you mind sharing more details on steps to reproduce your issue, the env info, cluster version, etc? Thanks

@cici37
Copy link
Contributor

cici37 commented Dec 22, 2022

Never mind. I saw the test you are trying to run regarding the flaky result mentioned.

Hi @inteon Thanks for raising the issue. I have tested with the CRD from your repo here and it is working fine with my 1.26 cluster. Would you mind sharing more details on steps to reproduce your issue, the env info, cluster version, etc? Thanks

@inteon
Copy link
Member Author

inteon commented Dec 22, 2022

Never mind. I saw the test you are trying to run regarding the flaky result mentioned.

Hi @inteon Thanks for raising the issue. I have tested with the CRD from your repo here and it is working fine with my 1.26 cluster. Would you mind sharing more details on steps to reproduce your issue, the env info, cluster version, etc? Thanks

Are you able to reproduce the issue?

@inteon inteon mentioned this issue Dec 29, 2022
Merged
@inteon
Copy link
Member Author

inteon commented Dec 29, 2022 •
edited

@cici37 @liggitt I found the root cause!: google/cel-go#620

@liggitt
Copy link
Member

liggitt commented Dec 29, 2022

Excellent find, thanks!

@jpbetz
Copy link
Contributor

jpbetz commented Jan 3, 2023

Wow, thanks for root causing this Tim!

@fedebongio
Copy link
Contributor

/assign @jpbetz @cici37
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 3, 2023
This was referenced Jan 5, 2023
Merged
Merged
Merged
Merged
This was referenced Nov 17, 2023
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpbetz jpbetz

@cici37 cici37

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bump cel-go bump to 0.12.6 to fix bug in cel-go jpbetz/kubernetes
6 participants
@jpbetz @liggitt @fedebongio @cici37 @k8s-ci-robot @inteon