vNets in Block becoming unassociated and cant be associated again

Open
#329 1 comment 0 reactions 1 assignee View on GitHub

@DCMattyG is already working on this.

Since Oct 3, 2024.

Assessment

This issue has not been assessed yet.

Description

help wanted

Describe the bug
We have an issue where some vNets are suddenly getting unassociated to the block. When we try to associate the vNet again, we get the following error: {"error":"Block already contains network(s) and/or reservation(s) within the CIDR range of target network."}.

When we look in CosmosDB we can see that the vNet actually still is in block, but it is ("active": false).

We can fix the issue by manually removing the vNet entry from CosmosDB and then associate the vNet again.

But then a day after, we suddenly have another vNet that's changed to ("active": false) and becomes unassociated.

To Reproduce
Steps to reproduce the behavior:

  1. vNet is suddenly unassociated.
  2. vNet can't be added again, because of error {"error":"Block already contains network(s) and/or reservation(s) within the CIDR range of target network."}.
  3. Checking CosmosDB, we can see the vNet is actually still there, but with ("active": false).

Expected behavior
We expect vNet to not change from ("active": true) to ("active": false).

Version
{
"status": "OK",
"version": "3.4.0",
"stack": "LegacyCompose",
"environment": "AZURE_PUBLIC",
"container": {
"image_id": "debian",
"image_version": "12",
"image_codename": "bookworm",
"image_pretty_name": "Debian GNU/Linux 12 (bookworm)"
}
}

Dominant language
JavaScript
Stars
327
Forks
111
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/ipam

All issues in Azure/ipam

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.