Closed danipber closed 1 year ago
Thanks @danipber for opening this pr, I've tried the following code but I couldn't reproduce this issue:
provider "azurerm" {
features {}
}
resource "azurerm_resource_group" "one" {
location = "eastus"
name = "zjhe-f18764-1"
}
resource "azurerm_virtual_network" "virtual_network_1" {
name = "vnet-1"
location = "eastus"
resource_group_name = azurerm_resource_group.one.name
address_space = ["192.168.0.0/16"]
}
resource "azurerm_resource_group" "two" {
location = "eastus"
name = "zjhe-f18764-2"
}
resource "azurerm_virtual_network" "virtual_network_2" {
address_space = ["10.0.0.0/16"]
location = "eastus"
name = "vnet-2"
resource_group_name = azurerm_resource_group.two.name
}
resource "azurerm_virtual_network_peering" "windows_agent" {
name = "peertowindowsagent"
resource_group_name = azurerm_resource_group.one.name
virtual_network_name = azurerm_virtual_network.virtual_network_1.name
remote_virtual_network_id = azurerm_virtual_network.virtual_network_2.id
}
resource "azurerm_virtual_network_peering" "linux_agent" {
name = "peertolinuxagent"
resource_group_name = azurerm_resource_group.two.name
virtual_network_name = azurerm_virtual_network.virtual_network_2.name
remote_virtual_network_id = azurerm_virtual_network.virtual_network_1.id
}
Could you please give me a minimum sample that could reproduce this issue with instructions for every step? Thanks!
Thanks for opening this issue. Since time has passed and @lonegunmanb was not able to reproduce this issue, I am going to mark this issue closed as “can’t reproduce”. If you are able to provide more information to help us reproduce this issue we may re-open this issue or open a new issue, thanks!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
1.2.4
AzureRM Provider Version
3.26.0
Affected Resource(s)/Data Source(s)
azurerm_virtual_network_peering
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Azure virtual network peering created
Actual Behaviour
Plugin did not respond https://dev.azure.com/bavelpay/Payments/_build/results?buildId=763&view=logs&j=30258c87-fa2d-5a55-b28f-ceed67c0ba10&t=c02799de-7530-5c13-7ab8-4e57dbaae743&l=72
Steps to Reproduce
module.virtual_network.azurerm_virtual_network.virtual_network will be updated in-place
~ resource "azurerm_virtual_network" "virtual_network" { id = "/subscriptions/xxxxxxxxxxxxxxx/resourceGroups/rg-bp-we-payments-d-01/providers/Microsoft.Network/virtualNetworks/vnet-bp-we-payments-d-01" name = "vnet-bp-we-pay-d-01"
module.virtual_network.azurerm_virtual_network_peering.linux_agent will be created
resource "azurerm_virtual_network_peering" "linux_agent" {
module.virtual_network.azurerm_virtual_network_peering.windows_agent will be created
Plan: 2 to add, 1 to change, 0 to destroy.
Important Factoids
No response
References
No response