-
Notifications
You must be signed in to change notification settings - Fork 30
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
SEGV when executing Rancher QuickStart #80
Comments
Hi, What terraform version is this? |
|
@mkysel if you have a terraform.tfstate file in there, delete it. That helped me! |
I'm getting this error when doing |
I just tried applying some cert-manager CRDs with the Rancher QSG and had no issues, Terraform version 1.0.2 and k8s version v0.8.2. The error comes deeply from the k8s library we use in the provider:
I wonder what could be the issue here, maybe the cluster is inaccessible for a moment, have you tried it several times? |
I have tried it multiple times over the course of about 2 days. Always the same result on the same machine in the same environment. I tried it today, still SEGVs. |
I have the same issue running a terraform apply having previously run a terrafrom destroy, so it's not an issue with the cluster being inaccessible. As @dominicrico says issue is only there when tfstate file are present. The version of |
I am getting this error when trying to switch from S3 remote to Terraform Cloud:
|
I've forked the provider and updated sigs.k8s.io/controller-runtime. It did not solve the problem but allowed me to get to the bottom of it. I realized that the Kubernetes API server was returning an Unauthorized response and I needed to update aws-auth secret to include the user which AWS token I was using. After doing this, the problem was fixed. Here's my fork if anyone needs it: https://registry.terraform.io/providers/andreychernih/k8s/latest
|
Describe the bug
Both
0.8.2
and0.9.1
crash.Steps to reproduce the issue:
Run the Rancher quickstart AWS
https://github.com/rancher/quickstart/tree/master/aws
Expected behavior
No SEGV.
The text was updated successfully, but these errors were encountered: