Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deployment failed; but get RequestFailedException with bad response message #44008

Open
xula2018 opened this issue May 13, 2024 · 4 comments
Open
Assignees
Labels
ARM customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@xula2018
Copy link

xula2018 commented May 13, 2024

Library name and version

Azure.Core 1.39.0
Azure.ResourceManager 1.11.1
Azure.ResourceManager.Resources 1.7.2

Describe the bug

Try to create a spot VM using template deployment, it failed due to low spot price. In Azure activity log, it shows the reason as "
Unable to perform operation 'Create VM' since the provided max price '0.001 USD' is lower than the current spot price '0.0113 USD' for Azure Spot VM size 'Standard_D2ds_v5'.".

However in the exception message from SDK, it says:
"Azure.RequestFailedException: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.
Status: 200 (OK)
ErrorCode: DeploymentFailed

Service request succeeded. Response content and headers are not included to avoid logging sensitive data."

Why doesn't it include the actual failure message?

Expected behavior

Previously we get exception with message like:

Azure.RequestFailedException: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.
Status: 200 (OK)
ErrorCode: DeploymentFailed

Content:
{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Resources/deployments/xxx","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"OperationNotAllowed","message":"Unable to perform operation 'Create VM' since the provided max price '0.001 USD' is lower than the current spot price '0.0113 USD' for Azure Spot VM size 'Standard_D2ds_v5'. For more information, see http://aka.ms/AzureSpot/errormessages."}]}}

Actual behavior

With Azure.Core 1.39.0, we get:

Azure.RequestFailedException: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.
Status: 200 (OK)
ErrorCode: DeploymentFailed

Service request succeeded. Response content and headers are not included to avoid logging sensitive data.

Reproduction Steps

at Azure.Core.OperationInternal1.GetResponseFromState(OperationState1 state)
at Azure.Core.OperationInternal1.<UpdateStatusAsync>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Azure.Core.OperationInternalBase.<UpdateStatusAsync>d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Azure.Core.OperationPoller.<WaitForCompletionAsync>d__10.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Azure.Operation.<WaitForCompletionResponseAsync>d__14.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.ValueTask1.get_Result()
at Citrix.AzureFacade.AzureResourceManager.ClientWrappers.LongRunningOperationExtensions.d__0.MoveNext()

Environment

No response

@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 13, 2024
@jsquire jsquire self-assigned this May 13, 2024
@jsquire
Copy link
Member

jsquire commented May 13, 2024

Hi @xula2018. Thanks for reaching out and we regret that you're experiencing difficulties. In order to triage this to the right folks to assist, I'll need you to tell me the Azure SDK package and version that you're using. Azure.Core is an infrastructure library that provides network operations for the Azure SDK, not something that you would use directly in your application.

@jsquire jsquire added needs-author-feedback More information is needed from author to address the issue. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels May 13, 2024
Copy link

Hi @xula2018. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

@jsquire jsquire assigned ArthurMa1978 and unassigned jsquire May 14, 2024
@jsquire jsquire added ARM Mgmt This issue is related to a management-plane library. needs-team-attention This issue needs attention from Azure service team or SDK team and removed needs-author-feedback More information is needed from author to address the issue. labels May 14, 2024
@jsquire
Copy link
Member

jsquire commented May 14, 2024

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@xula2018
Copy link
Author

Hi @xula2018. Thanks for reaching out and we regret that you're experiencing difficulties. In order to triage this to the right folks to assist, I'll need you to tell me the Azure SDK package and version that you're using. Azure.Core is an infrastructure library that provides network operations for the Azure SDK, not something that you would use directly in your application.

FYI, I added the SDK package and version to the ticket.

  • Azure.ResourceManager 1.11.1

  • Azure.ResourceManager.Resources 1.7.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARM customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

4 participants