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

Redis is busy processing a previous update request or is undergoing system maintenance. #1760

Open
onionhammer opened this issue Aug 8, 2023 · 4 comments

Comments

@onionhammer
Copy link

Bicep version
Bicep CLI version 0.20.4 (c9422e016d)

Describe the bug
Not sure where to report this, but I feel like there must be upstream channels here; when running the below bicep script, it works the first time, then fails to work any subsequent times with an error saying that redis is busy, unless I comment out the identityAssignment resource.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy the below bicep file once, it should work
  2. Deploy the below bicep file again after the first deployment, it should error.
param name string
param location string

@allowed(['C', 'P'])
param family string = 'C'
param capacity int = 0
@allowed(['Basic', 'Standard', 'Premium'])
param sku string = 'Basic'

param identityObjectId string
param identityName string

resource redis 'Microsoft.Cache/redis@2023-05-01-preview' = {
  name: name
  location: location
  properties: {
    enableNonSslPort: false
    redisConfiguration: {
      'aad-enabled': 'true'
    }
    sku: {
      family: family
      capacity: capacity
      name: sku
    }
  }

  resource identityAssignment 'accessPolicyAssignments' = {
    name: identityObjectId
    properties: {
      accessPolicyName: 'Data Contributor'
      objectId: identityObjectId
      objectIdAlias: identityName
    }
  }
}

output id string = redis.id
output hostName string = redis.properties.hostName
output port int = redis.properties.port
@onionhammer onionhammer changed the title Rredis is busy processing a previous update request or is undergoing system maintenance. Redis is busy processing a previous update request or is undergoing system maintenance. Aug 8, 2023
@stephaniezyen stephaniezyen transferred this issue from Azure/bicep Aug 9, 2023
@github-project-automation github-project-automation bot moved this to Todo in Bicep Aug 9, 2023
@stephaniezyen
Copy link
Contributor

I would open a support ticket and route it to the redis team on this issue. In the meantime, we will try to route this issue to that team.

@microsoft-github-policy-service
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @yegu-ms. Please see https://aka.ms/biceptypesinfo for troubleshooting help.

@arealmaas
Copy link

Any update on this? Or where is it possible to follow this issue?

arealmaas added a commit to Altinn/dialogporten that referenced this issue Mar 6, 2024
Getting this error when trying to deploy apps:

https://github.com/digdir/dialogporten/actions/runs/8170065128/job/22338884530
```shell
Error: ERROR: {"status":"Failed","error":{"code":"DeploymentFailed",
"target":"/subscriptions/***/resourceGroups/***/providers/Microsoft.Resources/deployments/dp-be-test-web-api-eu-1.0.4-2a8fa76",
"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":"Conflict",
"message":"The resource '/subscriptions/***/resourceGroups/***/providers/Microsoft.Cache/Redis/***' 
is busy processing a previous update request or is undergoing system maintenance.  
As such, it is currently unable to accept the update request.  
Please try again later.\r\nRequestID=4f32c560-a4bf-43b2-a87b-a2d727f68448"}]}}
```
There are two apps trying to update policies for the Redis-instance, and
since we cannot allow two deployment operations at once, we need to run
the deployment in sequence 👎

It might also be this issue, but let's try to set max-parallel and see
what happens. Azure/bicep-types-az#1760

If the case is that it is this issue 👆 We would need to click-ops that
part until it is fixed..
@cbou
Copy link

cbou commented Sep 6, 2024

I "solved" it by redeploying the deployment multiple times. Not the wished solution but it worked. Once it's created that's ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

4 participants