Closed idrissneumann closed 3 months ago
Other details, an issue has been opened here: https://github.com/pulumi/pulumi-terraform-bridge/issues/2257#issuecomment-2255327338
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: https://github.com/scaleway/terraform-provider-scaleway/pull/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:
The origin of your problem is partly linked to the change in bootscript support: https://www.scaleway.com/en/docs/compute/instances/troubleshooting/bootscript-eol/#migration-options-for-instances-using-bootscripts
I still think upgrading to the 2.42.1
of terraform provider should solve this issue.
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.
Thanks a lot @ringods and @dirien <3
Once it's released I'll post the results of our tests here
@idrissneumann done!
Feedback: it works like a charm, thanks a lot @ringods and @dirien <3
@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.