-
Notifications
You must be signed in to change notification settings - Fork 11
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
Runtime error "runtime error: invalid memory address or nil pointer dereference" on provisioning instances #321
Comments
Other details, an issue has been opened here: pulumi/pulumi-terraform-bridge#2257 (comment) But like I said I have the feeling it's more an issue of Scaleway changing their IaaS interface contract, so that's why I opened one here. Also, the resources are still created on Scaleway: ![]() But only the floating ip are attached to the state (when we delete the stack only the floatting ip is deleted): ![]() |
This issue might be the cause: scaleway/terraform-provider-scaleway#2664 "Bootscript" seems deprecated and has probably been removed from the response body which might cause the segfault. This has been released in the 2.42.1 version of the terraform provider, I think an upgrade might resolve the issue. |
Feedback from Scaleway:
I still think upgrading to the |
Btw I also tried to do it myself using: $ upgrade-provider pulumiverse/pulumi-scaleway --kind provider But I got this error: error: failed to gather package metadata: problem gathering data sources: 2 errors occurred:
* TF data source "scaleway_iam_api_key" not mapped to the Pulumi provider
* TF data source "scaleway_vpc_routes" not mapped to the Pulumi provider
make: *** [tfgen] Error 255 Not skilled enough yet to know how to fix this, otherwise it'd be with pleasure 😅 |
Hi, thanks @dirien for the PR <3 Any idea on when I might be merged ? Because all deployments on Scaleway are broken for everybody ^^ I'm also looking for a workaround in the meantime we can already apply Thanks! |
@idrissneumann I asked @ringods do have a look as soon he can. |
@idrissneumann done! |
@idrissneumann great! |
Hi.
Since few days, we got this error with a two-years running service:
We were using the 1.7.0 version package from
lbrlabs
but we upgraded to the 1.14.0 of this package and have exactly the same issue with this piece of code:And in the requirements.txt:
Because we got this error also with an old package, I bet Scaleway has changed something in their IaaS API http response which is badly catched in the go code but require an upgrade in this package.
Thanks in advance.
The text was updated successfully, but these errors were encountered: