Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

AutoStop fails with a 409 Conflict warning and BadRequest error in CreateAutoStopAlertExecutor

Open
  • Is something wrong?
#94 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
cloud

Research direction

Start with the CreateAutoStopAlertExecutor logs and the related issues #93 and #69, then investigate the Azure Tables 409 response alongside the alert-creation BadRequest. Reproduce the failed AutoStop deployment if possible and trace the executor's request path. Done means the alert is created successfully and the VM AutoStop workflow completes without these errors.

Written by the indexing model from the issue text.

Description

I've deployed this solution yesterday, however the AutoStop functionality isn't working (the VM doesn't stop). All function report successful execution, except for CreateAutoStopAlertExecutor, which logs the following:

2023-05-24T21:53:26Z   [Information]   Request [caacb797-301d-4045-894c-a3e5b6f58616] POST https://<REDACTED>.table.core.windows.net/Tables?$format=REDACTED
x-ms-version:REDACTED
DataServiceVersion:REDACTED
Accept:application/json; odata=minimalmetadata
x-ms-client-request-id:caacb797-301d-4045-894c-a3e5b6f58616
x-ms-return-client-request-id:true
User-Agent:azsdk-net-Data.Tables/12.6.1,(.NET 6.0.16; Microsoft Windows 10.0.14393)
x-ms-date:REDACTED
Authorization:REDACTED
Content-Type:application/json; odata=nometadata
client assembly: Azure.Data.Tables
2023-05-24T21:53:26Z   [Warning]   Error response [caacb797-301d-4045-894c-a3e5b6f58616] 409 Conflict (00.0s)
Cache-Control:no-cache
Transfer-Encoding:chunked
Server:Windows-Azure-Table/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id:1d2ef93d-6002-0037-188a-8e7a5b000000
x-ms-client-request-id:caacb797-301d-4045-894c-a3e5b6f58616
x-ms-version:REDACTED
X-Content-Type-Options:REDACTED
Date:Wed, 24 May 2023 21:53:24 GMT
Content-Type:application/json; odata=minimalmetadata; streaming=true; charset=utf-8
2023-05-24T21:53:26Z   [Information]   Executing 'CreateAutoStopAlertExecutor' (Reason='New queue message detected on 'create-alert-request'.', Id=71249287-9dff-4df8-9e4d-55d9c7744813)
2023-05-24T21:53:26Z   [Information]   Trigger Details: MessageId: 536094c3-3aa1-461c-a3cd-7b4df73bf2d5, DequeueCount: 3, InsertedOn: 2023-05-24T21:49:59.000+00:00
2023-05-24T21:53:26Z   [Information]   AutoStop: Attempted the create alert action on vm /subscriptions/<REDACTED>/resourceGroups/<REDACTED>/providers/Microsoft.Compute/virtualMachines/<REDACTED>:
2023-05-24T21:53:26Z   [Error]   Alert creation failed for /subscriptions/<REDACTED>/resourceGroups/<REDACTED>/providers/Microsoft.Compute/virtualMachines/<REDACTED>, exception message: Operation returned an invalid status code 'BadRequest'
2023-05-24T21:53:26Z   [Error]   Executed 'CreateAutoStopAlertExecutor' (Failed, Id=71249287-9dff-4df8-9e4d-55d9c7744813, Duration=423ms)

I am also unable to re-deploy the solution, as per #93.
Related issue: #69

Do you have any advice on how to proceed?

Dominant language
No language data
Stars
58
Forks
35
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 microsoft/startstopv2-deployments

All issues in microsoft/startstopv2-deployments

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.