-
Notifications
You must be signed in to change notification settings - Fork 113
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
Job with unreachable cluster causes a panic #3022
Labels
impact/panic
This bug represents a panic or unexpected crash
kind/bug
Some behavior is incorrect or out of spec
p1
A bug severe enough to be the next item assigned to an engineer
resolution/fixed
This issue was fixed
Comments
sinhalvi
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
May 23, 2024
Thanks for reporting this error @sinhalvi and apologies that you're facing it. After tracing through the logs, it appears that this error occurs in a very specific scenario. The following events must occur for the panic to occur.
To address this, we will need to add a clusterUnreachable check prior to checking the live cluster for the job's status. |
rquitales
added
p1
A bug severe enough to be the next item assigned to an engineer
impact/panic
This bug represents a panic or unexpected crash
and removed
needs-triage
Needs attention from the triage team
labels
May 24, 2024
rquitales
changed the title
panic: runtime error
Job with unreachable cluster causes a panic
May 24, 2024
rquitales
added a commit
that referenced
this issue
May 24, 2024
rquitales
added a commit
that referenced
this issue
May 24, 2024
rquitales
added a commit
that referenced
this issue
May 28, 2024
rquitales
added a commit
that referenced
this issue
May 28, 2024
rquitales
added a commit
that referenced
this issue
May 28, 2024
…3024) ### Proposed changes This PR ensures that we do not make a k8s API request during the provider's diff if there is an unreachable cluster. This currently occurs when the Pulumi program contains a Job resource with the `replaceUnready` annotation set to true. A panic would occur if we attempt to make the API call since our clients are nil. #### Testing done: 1. Created a repro test case that fails with a panic (https://github.com/pulumi/pulumi-kubernetes/actions/runs/9228447658/job/25392833842?pr=3024) 2. Added logic to prevent the panic, and test passes subsequently without intervention (https://github.com/pulumi/pulumi-kubernetes/actions/runs/9228685506/job/25393667599?pr=3024) 3. Manual validation to ensure panic isn't trigerred. ### Related issues (optional) Fixes: #3022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
impact/panic
This bug represents a panic or unexpected crash
kind/bug
Some behavior is incorrect or out of spec
p1
A bug severe enough to be the next item assigned to an engineer
resolution/fixed
This issue was fixed
What happened?
Hi, I suddenly see this error when I do a pulumi up on a stack
Example
I am using job resource from
import { Job } from '@pulumi/kubernetes/batch/v1'
Output of
pulumi about
It was working before and I have no changes in code or packages. I did upgrade pulumi and other and this is my env
CLI
Version 3.116.1
Go Version go1.22.3
Go Compiler gc
Plugins
KIND NAME VERSION
resource aws 6.18.0
resource docker 4.5.1
resource kubernetes 4.12.0
language nodejs unknown
Host
OS darwin
Version 12.6.8
Arch x86_64
This project is written in nodejs: executable='/usr/local/bin/node' version='v21.7.2'
Current Stack:
OPP TYPE URN
Backend
Name 2030009945
URL s3://
User sindhu.halvi
Organizations
Token type personal
Dependencies:
NAME VERSION
@pulumi/kubernetes 4.12.0
@pulumi/pulumi 3.105.0
@types/node 18.19.6
ts-deepmerge 6.2.0
ts-node 10.9.2
typescript 5.3.3
@pulumi/aws 6.18.0
@pulumi/docker 4.5.1
prettier 3.2.1
Additional context
one of the error logs shows this
I have tried everthing from updating, re-installing. nothing solves this issue
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: