Azure / Azure/bicep-registry-modules

[AVM CI Environment Issue]: Error when checking deployment status

Open
#2,865 5 comments 0 reactions 0 assignees Claimed by @AlexanderSehr View on GitHub
Needs: Core Team :genie: Type: AVM :a: :v: :m: Type: Bug :bug: Type: CI :rocket:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [X] I have checked for previous/existing GitHub issues

### Issue Type?

Bug

### Description

There is an intermittent error that can occur when checking the deployment status during CI:

```
VERBOSE: 12:13:38 - Checking deployment status in 8 seconds
VERBOSE: Resource deployment Failed.. (1/3) Retrying in 5 Seconds..

VERBOSE: An error occurred while sending the request.

VERBOSE: Deploying with deployment name [a-p-ap-b-max-t2-20240729T1207070374Z]
VERBOSE: Setting context to subscription [***]
VERBOSE: Using Bicep v0.29.47
...
...
```

When this occurs, a new deployment is started, however the first deployment is actually still ongoing. The second deployment is then likely to fail because there are essentially two deployments going on at the same time.

Perhaps a retry could be added when checking the deployment status?

Contributor guide

Open the contributing guide

Research direction

Start by reading linked pull request #4205 and the CI code that checks deployment status; the issue does not name a file or test. Reproduce or trace the intermittent request error and verify that status checking handles it without starting overlapping deployments.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
ci-cd, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.