Skip to content
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 while creating hpc nfs target resource #21139

Open
1 task done
aj1319 opened this issue Mar 27, 2023 · 5 comments
Open
1 task done

Error while creating hpc nfs target resource #21139

aj1319 opened this issue Mar 27, 2023 · 5 comments

Comments

@aj1319
Copy link

aj1319 commented Mar 27, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Getting the error while creating hpc_cahce_nfs_target:-

"Error: waiting for creation of Storage Target: (Name "hpcajhpc2” / Cache Name “hpccnajhpe1” / Resource Group "rgajhpcll"):
Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc2’".

But when creating manually with the same details, the resource gets created.

Terraform Version

1.3.7

AzureRM Provider Version

3.33.0

Affected Resource(s)/Data Source(s)

azurerm_hpc_cache_nfs_target

Terraform Configuration Files

Getting the error while creating hpc_cahce_nfs_target:-

"Error: waiting for creation of Storage Target: (Name "hpcajhpc2” / Cache Name “hpccnajhpe1” / Resource Group "rgajhpcll"):
Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc2’".

But when creating manually with the same details, the resource gets created.

Debug Output/Panic Output

N/A

Expected Behaviour

the resource hpc_cache_nfs_target should be created.

Actual Behaviour

Getting the error while creating hpc_cahce_nfs_target:-

"Error: waiting for creation of Storage Target: (Name "hpcajhpc2” / Cache Name “hpccnajhpe1” / Resource Group "rgajhpcll"):
Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc2’".

But when creating manually with the same details, the resource gets created.

Steps to Reproduce

Getting the error while creating hpc_cahce_nfs_target:-

"Error: waiting for creation of Storage Target: (Name "hpcajhpc2” / Cache Name “hpccnajhpe1” / Resource Group "rgajhpcll"):
Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc2’".

But when creating manually with the same details, the resource gets created.

Important Factoids

N/A

References

N/A

@aj1319 aj1319 added the bug label Mar 27, 2023
@github-actions github-actions bot removed the bug label Mar 27, 2023
@myc2h6o
Copy link
Contributor

myc2h6o commented Mar 29, 2023

Hi @aj1319 can you share the config you used which has the error? And set the environment variable TF_LOG to DEBUG to capture the API request detail. And as the error code AscInternalError sounds like there is an error within Azure itself rather than in the provider, I'd suggest opening a support to Azure as well for troubleshooting.

@aj1319
Copy link
Author

aj1319 commented Apr 3, 2023

Below are the results as requested from TF_LOG:-

2023-04-03T17:17:35.153+0530 [ERROR] provider.terraform-provider-azurerm_v3.33.0_x5.exe: Response contains error diagnostic: @module=sdk.proto diagnostic_severity=ERROR diagnostic_summary="waiting for creation of Storage Target: (Name "hpcajhpc1" / Cache Name "hpccnajhpc1" / Resource Group "rgajhpc11"): Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc1'."" tf_proto_version=5.3 tf_provider_addr=provider tf_resource_type=azurerm_hpc_cache_nfs_target @caller=github.com/hashicorp/terraform-plugin-go@v0.14.1/tfprotov5/internal/diag/diagnostics.go:55 diagnostic_detail= tf_req_id=21dde551-6c59-8345-16cb-c875c96101a2 tf_rpc=ApplyResourceChange timestamp=2023-04-03T17:17:35.144+0530
2023-04-03T17:17:35.175+0530 [ERROR] vertex "module.hpc_cache_nfs_target.azurerm_hpc_cache_nfs_target.hpc_cache_nfs_target["hpc_cache_nfs_target_1"]" error: waiting for creation of Storage Target: (Name "hpcajhpc1" / Cache Name "hpccnajhpc1" / Resource Group "rgajhpc11"): Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc1'."

│ Error: waiting for creation of Storage Target: (Name "hpcajhpc1" / Cache Name "hpccnajhpc1" / Resource Group "rgajhpc11"): Code="AscInternalError" Message="Error encountered deploying the storage target: 'hpcajhpc1'."

│   with module.hpc_cache_nfs_target.azurerm_hpc_cache_nfs_target.hpc_cache_nfs_target["hpc_cache_nfs_target_1"],
│   on ..\main.tf line 6, in resource "azurerm_hpc_cache_nfs_target" "hpc_cache_nfs_target":
│    6: resource "azurerm_hpc_cache_nfs_target" "hpc_cache_nfs_target" {


2023-04-03T17:17:35.192+0530 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF" 
2023-04-03T17:17:35.228+0530 [DEBUG] provider: plugin process exited: path=.terraform/providers/registry.terraform.io/hashicorp/azurerm/3.33.0/windows_amd64/terraform-provider-azurerm_v3.33.0_x5.exe pid=3496
2023-04-03T17:17:35.229+0530 [DEBUG] provider: plugin exited/

@aj1319
Copy link
Author

aj1319 commented Apr 5, 2023

@myc2h6o any update on this.

@myc2h6o
Copy link
Contributor

myc2h6o commented Apr 6, 2023

@aj1319 the given log looks not providing more useful info unfortunately. The AscInternalError looks something from the resource itself so probably you need reach out to Azure support for further troubleshooting. From the provider side, if you could share the Terraform config you were using, we could try in our environment and see if it could work. Besides that, the Debug log shall have the API request details (Put request body), if you could also capture that, it could be tried with sending the REST API directly to see if works or not.

@arjenkins25
Copy link

Has there been any potential updates on this? I ran into this error today as well and was wondering if it was bug or an issue on my end. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants