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
SIGSEGV on refresh state #359
Comments
Hey @repomaa, would it be possible that you provide a minimal reproducible configuration? On the first view, it looks like your certificate is not PEM encoded (or maybe wrong encoded). The nil pointer will be fixed, to fix this we would need a reproducible config. |
Hm it should be pem encoded, i haven't changed anything and just added a few servers to the setup. Not sure if i can provide a minimal config, as it will mess up the state if i remove resources from it. |
This used to work fine i should add |
According to the documentation [`Decode`](https://pkg.go.dev/encoding/pem#Decode) returns nil if no pem data is found. Technically this is possible if the certificate we store in our API did not contain valid data, or some additional content after the PEM block. I'm currently not sure how to reproduce this, but this commit should at least get rid of the panic. Depending on the actual issue it might be better to return an error instead. Closes #359
Hi, @repomaa I have a preliminary fix in the works. But I'm unsure how to reproduce and subsequently test it. Could you send me the name of the affected project and your customer number to ferdinand.hofherr@hetzner-cloud.de? I guess you know this, but I have to write it anyways: please don't include any sensitive information like private keys or passwords. |
According to the documentation [`Decode`](https://pkg.go.dev/encoding/pem#Decode) returns nil if no pem data is found. This is possible if the certificate contains additional data which is not part of the certificate. If this data occurs at the end the code before this commit panics. This commit ensures that such data is ignored. Data between two certificates in the chain is ignored as well. Leading data leads to an error being returned. Closes #359
According to the documentation [`Decode`](https://pkg.go.dev/encoding/pem#Decode) returns nil if no pem data is found. This is possible if the certificate contains additional data which is not part of the certificate. If this data occurs at the end the code before this commit panics. This commit ensures that such data is ignored. Data between two certificates in the chain is ignored as well. Leading data leads to an error being returned. Closes #359
I'm encountering following error when refreshing the state for a hcloud project:
What can I do to get past this in the short term? I need to update this infrastructure asap.
The text was updated successfully, but these errors were encountered: