vNets in Block becoming unassociated and duplicated

[jkieffer0616]

Describe the bug
When I go in to Block Networks I will see a vNet in red with ErrNotFound but I will also see a different row with the exact same vNet that is unchecked (not associated) so I have to uncheck the Not Found one and check the found one to get it to associate again. Almost every day this happens and it's not always with the same vNets. Sometimes it's just one, sometimes it's more than one. Nothing has changed with the vNet on the Azure side except maybe creating/deleting subnets.

To Reproduce
Steps to reproduce the behavior:
Can't force it to reproduce but if I go to Block Networks I will see the duplicate vNets (one red with ErrNotFound, the other is not associated even though at one time it was associated)

Expected behavior
Once associated the vNet should stay associated until it association is removed.

Screenshots

[DCMattyG]

Hi @jkieffer0616, I was going through all of the current open issues & discussions and realized that I never responded to you on this item and I'm very sorry for that!

I did add some code fixes to the UI a while back to attempt to address this problem that you are seeing. Can you let me know if this is still happening in your environment? I definitely want to make sure we get to the bottom of this together as I'm never satisfied until all of the issues are addressed and everyone is having a great experience with the Azure IPAM solution.

Let me know if you're still seeing this and I'll make sure to focus on a proper resolution for you here. Thank you!

[jkieffer0616]

@DCMattyG - I will update to the latest code version, try it out, and let you know if I still see the issue. Thanks!

[DCMattyG]

Hey there @jkieffer0616, we've just released v3.0.0 so the latest containers are available.

Have you been able to test if the UI fixed I implemented have addressed your situation with the duplicate entries appearing?

Please let me know how things are going when you can, thanks!

[jkieffer0616]

@DCMattyG - I was able to update the containers and will keep an eye on it to see if it resolved the issue.

On a side note - is there an easy process to update from the multi-container deployment to the newer, single container deployment?

[DCMattyG]

Hi @jkieffer0616, so great to hear that you were able to update all of the containers!

I am working on a document to walk through all of the steps on converting the original 3-container deployment to the new single container model. I'm also working on a script that will do all of the work for you as well.

Will keep you posted as soon as both of those items are ready 👍