-
Notifications
You must be signed in to change notification settings - Fork 189
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
Error running aztfexport in RHEL8 #461
Comments
@cameronew This seems to be a network issue when downloading the provider. Did you try to remove the pre-installed provider in your environment, and download the provider again via |
@magodo Yes I deleted the provider and ran terraform init which worked fine then had th |
Do you have any special settings in your |
No just the defaults |
@cameronew Just want to check if you still have this issue, or I can close it now? |
I am seeing the same issue on RHEL9. It looks like /tmp is filling up. My /tmp is 2GB, however aztfexport seems to be repeatedly downloading the same provider into /tmp multiple times which fills it up. Running terraform init in the same directory works fine, so I am not sure what issue aztfexport is having. Any suggestions? Microsoft Azure Export for Terraform initializing provider for the import directories: 5 errors occurred: Error: Failed to install provider Error while installing hashicorp/azurerm v3.99.0: write
Error: Failed to install provider Error while installing hashicorp/azurerm v3.99.0: write
Error: Failed to install provider Error while installing hashicorp/azurerm v3.99.0: write
Error: Failed to install provider Error while installing hashicorp/azurerm v3.99.0: write
Error: Failed to install provider Error while installing hashicorp/azurerm v3.99.0: write |
I am not sure if this is related, but I tried the same thing on a Windows machine and get a step further, however now it appears that aztfexport is only configured to interact with the Azure Commercial Cloud API (management.azure.com). The subscription that I want to access is the Azure US Government Cloud, which uses this API URL management.usgovcloudapi.net. az cli uses the following to set this, and the terraform azurerm provider also supports this with the metadata_host parameter. Is there a way to set it with aztfexport?
|
@ryanhitch The first error is due to:
The second ask is now supported by: #546 |
@magodo Before I run aztfexport 1.9G is available in /tmp. "no space left on device" is caused by aztfexport downloading the azurerm provider repeatedly until there is no space left in /tmp. terraform init in the same directory just downloads the provider once, so I am not sure what aztfexport is doing. Thanks for #546 |
@ryanhitch Instead you can configure the terraform to cache the provider to avoid repeated download. |
By default it looks like aztfexport downloads 10 copies of the azurerm provider into /tmp when running 'aztfexport rg myResourceGroup' which I am guessing is to export 10 resources at a time. A default Azure RHEL9 VM image only has a 1GB /tmp partition which is likely why some people have had this issue. 2024-08-19T17:37:58.711Z [INFO] aztfexport: New resource group meta Error: Failed to install provider Error while installing hashicorp/azurerm v3.99.0: write |
Another way is to reduce the parallelism to a lower number (defaults to 10). |
Hi,
Having the following issue when using the tool. Terraform init works fine but it seems to have trouble when running a simple export.
See error below. The plug does seem to be installed ok.
aztfexport resource-group mytestrg
#error message
Microsoft Azure Export for Terraform
initializing provider for the import directories: 2 errors occurred:
* task error: error running terraform init: exit status 1
Error: Failed to install provider
Error while installing hashicorp/azurerm v3.65.0: unexpected EOF
Error: Failed to install provider
Error while installing hashicorp/azurerm v3.65.0: unexpected EOF
#plugin
-rwxr-xr-x 1 ewan ewan 194940928 Oct 5 12:55 terraform-provider-azurerm_v3.65.0_x5
[ewan@00f836ff2ebd linux_amd64]$ pwd
/home/ewan/test/.terraform/providers/registry.terraform.io/hashicorp/azurerm/3.65.0/linux_amd64
#terraform init seems ok
[ewan@00f836ff2ebd test]$ terraform init
Initializing the backend...
Initializing provider plugins...
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
[ewan@00f836ff2ebd test]$
The text was updated successfully, but these errors were encountered: