-
Notifications
You must be signed in to change notification settings - Fork 6
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
Network panics: can't convert "x86" to cty.Value #575
Comments
Hi @eBeyond. Thanks for opening an issue. I'm sorry that you are seeing a panic here. We will take a look as soon as possible. |
Hey @eBeyond, thanks for reporting. I'm failing to reproduce the issue. The resource provisions fine for me. Looking at the stack trace, it seems to suggest this is a problem with an Invoke, rather than the resource - are you using any functions somewhere in the program? Could you please post a program which exhibits the panic? |
I've found the issue. It wasn't related to this module. Someone created a pyproject.toml and a poetry.lock. That seems to be the reason. After changing the pulumi.yaml to utilize poetry it starts working. Sorry |
Glad you found a solution @eBeyond. The panic you got is not the desired experience we'd like users to see, so if you have any more details about how you got pulumi to panic that'd be helpful in making sure other users don't hit the same issue. Thanks! |
The last comment was wrong. It causes to reuse pretty old pulumi-hcloud. It was 1.17.1. If I immediatly updated to 1.20.0 I got the error again. After that I've tried to update release by release until 1.19.1. That was the last one working properly. If I do a pulumi refresh and pulumi up at this point I could update to 1.20.0. I think that it might be an issue with the state which could be outdated or not compatible with 1.20.0. But I'm not sure. After doing the refresh and up it was working as expected. |
When running 1.20.0 it sometimes work, sometimes not. I'm trying to setup a script to reproduce it. |
Okay, thanks. LMK if you find anything for us to dig into. |
I've found the real issue with this issue now:
it fail with the message:
It works as expected. I think this has to do with the lookup of the snapshots within the get_image() function. |
Thanks for getting back to us @eBeyond. Does the same thing happen if you specify the For maintainers: this might be related to pulumi/pulumi-terraform-bridge#2282 |
Does not work, error as described:
Works as expected:
|
Hi @eBeyond - thank you for your help in root causing this. It's looking like you have a workaround for now by specifying the architecture explicitly. It's looking like this will be resolved by pulumi/pulumi-terraform-bridge#2282. We'll update here as soon as we have a fix. |
Describe what happened
I've got a Network configuration like this:
This was working some time ago. But now (after an update) it failed:
Sample program
Log output
Affected Resource(s)
I can only see it failing on network until now.
Output of
pulumi about
Additional context
No response
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: