azure create volume failed with 513: InternalServerError - Error getting List

Lu, Lingli 0

Hi,

I met the errors below several days ago.

ajkuma 26,721 Reputation points Microsoft Employee

2024-10-16T08:22:11.23+00:00

Lu, Lingli, To better assist you on this, could you please let us know if you are performing this operation on an Azure VM or Azure Storage or some other service?

Kindly provide more details about your requirement/scenario, add a screenshot after concealing any private details.
Sumarigo-MSFT 47,101 Reputation points Microsoft Employee

2024-10-17T05:10:50.05+00:00

@Lu, Lingli Just checking in to see if you have had a chance to see the previous response. Could you share the above required information to understand/investigate this issue further?
Lu, Lingli 0 Reputation points

2024-10-17T06:13:25.2433333+00:00

Hi,

Thanks for checking.
The operation was called by some automation scripts(perl) which call the rest API (netapp volume create or update), then as it's async, we got the async uri from response header Azure-AsyncOperation to get the current operation status. The error was reported in the GET process. So far, we only see the error for this capacity pool. So not sure what happened.
KarishmaTiwari-MSFT 20,212 Reputation points Microsoft Employee

2024-10-18T22:44:09.36+00:00
@Lu, Lingli Looks like you are using Azure netapp files? Can you please share in detail, what you are trying to do, what steps are you following, any docs links, and at which step are you seeing the error? This would help us to redirect it to the right expert team for troubleshooting or reproduce the issue on our end.

Based on my understanding of the issue so far, I would recommend checking on the following and share the results:

If a volume create-read-update-delete (CRUD) operation is performed on a volume not in a terminal state, the operation will fail. Automation workflows and portal users should check for the terminal state of the volume before executing subsequent asynchronous operations on the volume. Ensure that the volume is in a terminal state before performing any CRUD operations.

Sometimes, internal server errors can be transient. Retrying the operation after some time might resolve the issue.

Enable debug logging in your automation scripts to get more detailed error messages.

https://learn.microsoft.com/en-us/azure/azure-netapp-files/troubleshoot-volumes
Lu, Lingli 0 Reputation points

2024-10-21T00:55:35.0833333+00:00

this ticket could be closed as I was contacted by Azure support this was an azure defect and was fixed several days ago. Thank you all.
Lu, Lingli 0 Reputation points

2024-10-21T00:57:48.2133333+00:00

Thank you for helping. This could be closed as I was contacted by Azure support that there was a bug in Azure side and was fixed several days ago. Thank you all.

1 answer

KarishmaTiwari-MSFT 20,212 Reputation points Microsoft Employee

2024-10-21T02:23:26.2966667+00:00

@Lu, Lingli
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Issue: For Azure Netapp files, azure create volume failed with 513: InternalServerError - Error getting List. The operation was called by some automation scripts(perl) which call the rest API (netapp volume create or update), then as it's async, we got the async uri from response header Azure-AsyncOperation to get the current operation status. The error was reported in the GET process. So far, we only see the error for this capacity pool.

Solution: Customer shared - "I was contacted by Azure support that there was a bug in Azure side and was fixed several days ago."

If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

azure create volume failed with 513: InternalServerError - Error getting List

1 answer

Your answer