Closed dimi4ik closed 10 months ago
Hi @dimi4ik,
Thanks for reporting the issue. From your terraform, looks like you are using the VNet name azurerm_virtual_network.example.name
on Azure to create the network interface. However, it should be one of the subnet available from the hypervisor resource pool you are using for the catalog.
Please refer to the documentation for the network
field in network_mapping
: https://registry.terraform.io/providers/citrix/citrix/latest/docs/resources/daas_machine_catalog#network
However, provider should have handled this case as an error and fail the terraform apply job, instead of just crashing. We will address this in the next release.
Thank you!
hi @zhuolun-citrix, Thanks, that was my typo, I actually assigned the wrong network.
Terraform Core Version
he semantic version of Terraform Core used when experiencing the bug. If multiple versions have been tested, a comma separated list.
Terraform v1.5.6 on linux_amd64
Description
The Terraform plan works and shows the data for new MC, but when I create a new MC I get the following error
error: Unexpected error in the Citrix provider
If you need further logs/data from me, please send me a PM
Affected Resource(s)
Please list the affected resource(s) and/or data source(s). citrix_daas_machine_catalog
Expected Behavior
What should have happened? a new MC should be created.
Relevant Error/Panic Output Snippet
If applicable, provide a relevant snippet from the error or panic output. This will be rendered as shell, so there is no need to add a
Terraform Configuration Files
Debug Output
Panic Output
If Terraform produced a panic, please paste, upload, or link to a file or Gist containing the output of the crash.log.