-
Notifications
You must be signed in to change notification settings - Fork 686
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
Using baremetal provider from behind an explicit proxy times out #48
Comments
v1.0.5 - Experiencing crashes with or without http_proxy or https:_proxy being set. 2017/04/03 06:41:21 [DEBUG] plugin: terraform-provider-baremetal_amd64: [signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0x939bbb]
!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!! Terraform crashed! This is always indicative of a bug within Terraform. When reporting bugs, please include your terraform version. That !!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!! |
Looking into this now |
I'm not able to reproduce this, but there is an edge case wherein we didn't check for errrors. If you run this with |
Also, please post your .tf file. I tried a volume attachment, but maybe there's different options or something. |
Bump |
Haven't been able to repo internally; need to setup a more restrictive proxy. |
Have not been able to reproduce the issue over the past few days. Access to api via proxy seems to be stable for now. |
@mrhearn Excellent! I'll close the ticket, please reopen it if the issue resurfaces. |
Is there support for an explicit proxy supporting the environment variables like:
export http_proxy=http://internal-web-proxy.example.com:80
export https_proxy=http://internal-web-proxy.example.com:80
Currently when behind a proxy server it just times out and does not appear to utilise the proxy environment variables.
From checking elsewhere it appears to need to be supported in the provider code not base Terraform code.
The text was updated successfully, but these errors were encountered: