getting internal server error while adding vNet to block using API about ipam HOT 6 CLOSED

Hi @vpgohil, looking at the line referenced in the error message above, it seems you may be running a previous version of the IPAM container. Please stop/start the Azure App Service, and give it a few minutes to download the latest version of the containers. Hopefully this will address your issue.

Just for your knowledge, when you add networks from the UI, it uses a PUT to update the entire list at once. This is why you were seeing a discrepancy between it working it the UI, and failing when you performed a POST locally.

from ipam.

@DCMattyG ,
Thanks for your quick response!

I did restart Azure App Service and I am still getting "internal error" for POST calls.

Am I missing something?

from ipam.

Hey @vpgohil, thanks for the feedback. It seems the latest source code may not have been built into the latest container images. I just built the new containers and pushed them to the ACR. Please try stopping/starting the App Service one more time to allow it to pull the new images, and then let me know if you're still experiencing the same behavior. Thanks for all of the feedback!

from ipam.

Hi @DCMattyG , I am still getting same error.

from ipam.

@vpgohil, I'm happy to do a 1:1 session with you to figure out why you're seeing this behavior. Please feel free to reach out to me at [email protected] so we can find a time that works best between us.

from ipam.

Hi @vpgohil, closing this issue as we spoke 1:1 and have confirmed this specific issue has been resolved. Please reach out if anything else comes up and we'll address it right away. Thanks!

from ipam.