Azure / Azure/ipam

Virtual networks not discoverable

Open
#200 5 comments 0 reactions 1 assignee Claimed by @DCMattyG View on GitHub
enhancement
Dominant language
JavaScript
Stars
327
Forks
111
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Virtual networks are not discoverable on blocks if external networks with overlapping CIDRs are associated with the block.

**To Reproduce**
I was trying to associate a new set of virtual networks CIDRs to an existing block when I realized the vnets were not discoverable. While checking the external networks, I found out some of them were overlapping with the vnets that wouldn't show up.
As a test, I removed those external vnets, refreshed the IPAM page (not just the network association refresh button) and the virtual networks showed up this time.

**Expected behavior**
Have all vnets discoverable even if they are conflicting with other vnets/external networks CIDRs.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.