Azure / Azure/azure-powershell

Property 'PeeredRemoteAddressSpace' not filled in Az.Network current released versions

Open
#27,585 4 comments 0 reactions 0 assignees View on GitHub
act-quality-productivity-squad bug customer-reported Network - Virtual Network Service Attention
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
3d 14h
Merged PRs (30d)
54

Description

### Description

The property '**PeeredRemoteAddressSpace**' is not filled when running the command **Get-AzVirtualNetworkPeering** -VirtualNetworkName $VirtualNetworkName -ResourceGroupName $ResourceGroupName.
This issue happens in Az.Network version 7.16.0, 7.15.1, 7.15.0, and 7.13.0. The issue didn't happen in Az.Network version 7.10.0 and 7.14.0. The versions not mentioned here weren't tested.

### Issue script & Debug output

```PowerShell
$virtualNetworkPeeringAll = Get-AzVirtualNetworkPeering -VirtualNetworkName $VirtualNetworkName -ResourceGroupName $ResourceGroupName

$virtualNetworkPeeringAll | format-List
```

### Environment data

```PowerShell
$PSVersionTable

Name Value
---- -----
PSVersion 7.5.0
PSEdition Core
GitCommitId 7.5.0
OS Microsoft Windows 10.0.20348
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
```

### Module versions

```PowerShell
Get-Module Az*

ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Script 4.1.0 Az.Accounts {Add-AzEnvironment, Clear-AzConfig, Clear-AzContext, Clear-AzDefault…}
Script 7.16.0 Az.Network {Add-AzApplicationGatewayAuthenticationCertificate, Add-AzApplicationGatewayBackendAddressPool, Add-AzApplicationGatewayBackendHttpSetting, Add-Az…
```

### Error output

```PowerShell
...
EnableOnlyIPv6Peering :
RemoteSubnetNames : {}
LocalSubnetNames : {}
RemoteGateways :
PeeredRemoteAddressSpace :
RemoteVirtualNetworkAddressSpace : Microsoft.Azure.Commands.Network.Models.PSAddressSpace
....
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing Get-AzVirtualNetworkPeering with Az.Network 7.16.0 and compare its output with versions 7.10.0 and 7.14.0. Trace how PeeredRemoteAddressSpace is populated for the returned virtual network peering object. Done means the property is filled with the expected remote address space in the affected released versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, powershell
Domain
cloud, networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.