Azure / Azure/ipam

Overlap in CIDR

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

Description

**Describe the bug**
There are some vnet's which got created with overlap CIDR ranges, and we can see both CIDRs are makred as associated as well.
**To Reproduce**
Steps to reproduce the behavior:
Not sure how to reproduce this as this is not permanent issue

**Expected behavior**
CIDRs shouldn't be overlapped atleast once those are associated to an existing vnets. Reservations shouldn;t evn provide those ranges

**Screenshots**

Image


⚠️ Found 5 overlap(s): just adding one here for security reason

OVERLAP DETECTED:
VNet 1: ***
Address Spaces: 10.43.2.192/26

VNet 2: ***
Address Spaces: 10.43.2.192/28

Overlapping CIDRs:
- 10.43.2.192/26 <-> 10.43.2.192/28


**Additional context**
We have observed this behaviour for few vnets as mentioned above.

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.