-
Notifications
You must be signed in to change notification settings - Fork 54
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
Can no longer run pulumi refresh/pulumi up after upgrading to pulumi-gcp 8.15.0. #2895
Comments
Hi @schplat, thank you for filing this issue. We understand that this is a frustrating experience. We see this kind of bug when a resource field has changed type in a certain way. |
Hello again - The team has taken a look at this and we cannot see anything immediately obvious that sticks out. This kind of error occurs when upstream changes the behavior of MaxItems = 1 between versions, and the culprit here is likely a single resource. We don't currently have a way of telling which resource is failing in this way, so in order for us to gain traction here we do need the following:
We're also working on better tooling around panics as a long-term investment to help with issues like this. Thank you for your patience! |
Upgrading from pulumi-gcp version 7.38.0 I will have to do the pulumi up at some point over the weekend. I managed to roll back to 7.38, and fortunately the state only needed to be modified in one location between the two versions to make it compatible with 7.38 again, I need it to be in a working state for the time being. The minimal repro will still be difficult, even from my end, as pulumi is managing ~40 resources even in its smallest stack configuration, and I have no idea which resource it's dying on. The panic is attached to the top level Stack URN on the output, so it's not like I can use that to even narrow it down.. Is there a bisection that can be done between 7.38.0 and 8.15.0 that might show which resources added a MaxItems = 1 in order to narrow down what I have to look for? |
@schplat we've added some instrumentation to narrow down the panic and label it with a specific resource type, name, and lifecycle method. https://github.com/pulumi/pulumi-gcp/tree/refs/tags/v8.17.0-alpha.2 version of the provider is available with this instrumentation, and this will be mainlined with v8.17.0. Unfortunately we were not able to repro as yet. There are too many resources involved in MaxItems=1. |
Describe what happened
Every run ends with the following error:
` Detected that /home/jnelson/.pulumi/plugins/resource-gcp-v8.15.0/pulumi-resource-gcp exited prematurely.
This is always a bug in the provider. Please report the issue to the provider author as appropriate.
Sample program
I'm not even sure what specific component is causing this, so can't really provide a sample program, and I'm not going to provide my entire code base here.
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
CLI
Version 3.147.0
Go Version go1.23.5
Go Compiler gc
Plugins
KIND NAME VERSION
resource gcp 8.15.0
resource mailgun 3.5.7
language python 3.147.0
Host
OS ubuntu
Version 22.04
Arch x86_64
This project is written in python: executable='/home/jnelson/git//venv/bin/python' version='3.10.12'
Additional context
While not happening on every stack I have, it is happening within a few stacks.
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: