-
Notifications
You must be signed in to change notification settings - Fork 155
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 on pulumi refresh after using @pulumi/aws provider 6.22.0 #3429
Labels
kind/bug
Some behavior is incorrect or out of spec
resolution/duplicate
This issue is a duplicate of another issue
Comments
davejhilton
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Feb 14, 2024
after creating this issue, I just saw #3421, which looks like it's the same issue |
Hey @davejhilton, yeah this looks very much like #3421. That issue is fixed in 6.22.1 - please update to that and LMK if you are still having the problem! I'll close this issue as a duplicate for now. |
VenelinMartinov
added
resolution/duplicate
This issue is a duplicate of another issue
and removed
needs-triage
Needs attention from the triage team
labels
Feb 15, 2024
looks like 6.22.1 fixes the issue. Thanks 👍 |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Some behavior is incorrect or out of spec
resolution/duplicate
This issue is a duplicate of another issue
What happened?
I'm getting a go panic every time running
pulumi refresh
on one of my stacks, using@pulumi/aws
provider version 6.22.0The output is this:
This panic happens consistently every time I try to run
pulumi refresh
on this stack. I cannot reproduce the issue on other stacks that are using earlier versions of this provider.Example
I'm not actually sure exactly how to reproduce this... other than:
@pulumi/aws
node module from6.13.2
to6.22.0
pulumi up
, which ONLY updates the provider versionpulumi refresh
this consistently causes the go panic.
If I revert to the older node module version, and then run
pulumi up
(to once again update the provider in my stack's state, to use the older version)... thenpulumi refresh
... it no longer panics.I can see that the error message mentions that the panic is happening inside of
elbv2.flattenLbForwardActionOneOf(...)
... but I haven't touched anything related to ALB listeners in quite some time.If more details are required about the ALB listener rules that we've got in place (or the URNs of specific resources, etc), I suppose I could try to include an (obfuscated) sample of what we're doing. Or, I can provide a more full sample, if it's through a less public channel than a github issue. Though to be honest, I have no idea which listener rules it would be breaking on, since we have several different listeners, each with different rules and configurations.
Output of
pulumi about
Additional context
I haven't had time to do a version "bisect", to see which is the earliest version of
@pulumi/aws
that starts causing the panic. Right now all I know is it's somewhere between6.13.2
(working) and6.22.0
(broken). But I can try messing with that tomorrow if I get some time.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: