-
Notifications
You must be signed in to change notification settings - Fork 409
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
Server is busy with another operation. Please try again later during the configuration step #4451
Comments
I'm using this bicep below and it crashes with the configuration step ('pgaudit.log').. server is « is busy with another operation. Please try again later." module postgres '../main.bicep' = {
name: 'postgres-${deploymentSuffix}'
params: {
resourceDescription: 'test'
location: location
name: name
administratorLogin: 'srvadmin'
administratorLoginPassword: 'Admin123'
skuname: 'Standard_D2ads_v5 (2 vCores, 8 GiB memory, 3200 max iops)'
storageSizeGB: 64
version: '11'
appid: appID
peSubnetResourceId: '/subscriptions/f5c25c0b-39d1-48b7-a644-c1f6b4d83b49/resourceGroups/rglabtic01vnet01/providers/Microsoft.Network/virtualNetworks/vnetcanadacentrallab01/subnets/snet-azu-canadacentral-lab-pe-l3kdp2'
databases: [
{
charset: 'UTF8'
collation: 'en_US.utf8'
name: name // Mettre le nom de la BD
}
]
configurations: [
{
name: 'pgaudit.log' <<<<<<<<<<<<
source: 'user-override'
value: 'DDL,MISC,ROLE'
}
{
name: 'pgaudit.log_client'
source: 'user-override'
value: 'ON'
}
{
name: 'pgaudit.role'
source: 'user-override'
value: 'azure_pg_admin'
}
]
}
} |
@Emile010530 - Hi. I am sorry for the deal in response to you. It looks like you opened a generic issue which doesn't get picked up by our automated system. I heard from Amani Chouchane this afternoon that you have this issue. Typically, the "Server is busy with another operation." is something related to the backend, within Azure and isn't something that we can control with Bicep and Azure Verified Modules. There are situations however where I have seen a similar error when assigning configurations that are not correct. Do you get the same error when running the script a second time? Do you get the same error if you remove the "configurations" section? Thanks |
Interne
Hello,
Thanks for the feedback.
Everything works if I run the script a second time and also it works the first time if I remove the configuration part.
Everything worked fine last year with one of the old versions (0.5.0) but not with the latest version (0.9.1).
Is it possible to fix the problem?
Thanks again
De : Nate Arnold ***@***.***>
Envoyé : 20 février 2025 18:56
À : Azure/bicep-registry-modules ***@***.***>
Cc : Mellus, Emile ***@***.***>; Mention ***@***.***>
Objet : Re: [Azure/bicep-registry-modules] Server is busy with another operation. Please try again later during the configuration step (Issue #4451)
Vous n’obtenez pas souvent d’e-mail à partir de ***@***.******@***.***>. Pourquoi c’est important<https://aka.ms/LearnAboutSenderIdentification>
ATTENTION ! CE COURRIEL PROVIENT DE L’EXTERNE
Avant d’ouvrir ou de télécharger une pièce jointe ou de cliquer sur un lien, assurez-vous que le courriel provient d’une personne ou une organisation de confiance.
Faites preuve de vigilance, développez les bons réflexes, et ne téléchargez aucune pièce jointe non sollicitée ! Au besoin, cliquez sur le bouton Signaler le message sur votre barre d'outils.
@Emile010530<https://github.com/Emile010530> - Hi. I am sorry for the deal in response to you. It looks like you opened a generic issue which doesn't get picked up by our automated system. I heard from Amani Chouchane this afternoon that you have this issue.
Typically, the "Server is busy with another operation." is something related to the backend, within Azure and isn't something that we can control with Bicep and Azure Verified Modules. There are situations however where I have seen a similar error when assigning configurations that are not correct. Do you get the same error when running the script a second time? Do you get the same error if you remove the "configurations" section? Thanks
—
Reply to this email directly, view it on GitHub<#4451 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPQN2AR55KKA7P26MUE32LL2QZTQNAVCNFSM6AAAAABXFH3QS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSHE3TMNJWGU>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
[arnoldna]arnoldna left a comment (Azure/bicep-registry-modules#4451)<#4451 (comment)>
@Emile010530<https://github.com/Emile010530> - Hi. I am sorry for the deal in response to you. It looks like you opened a generic issue which doesn't get picked up by our automated system. I heard from Amani Chouchane this afternoon that you have this issue.
Typically, the "Server is busy with another operation." is something related to the backend, within Azure and isn't something that we can control with Bicep and Azure Verified Modules. There are situations however where I have seen a similar error when assigning configurations that are not correct. Do you get the same error when running the script a second time? Do you get the same error if you remove the "configurations" section? Thanks
—
Reply to this email directly, view it on GitHub<#4451 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPQN2AR55KKA7P26MUE32LL2QZTQNAVCNFSM6AAAAABXFH3QS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSHE3TMNJWGU>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
I use flexible-server:0.9.1 module ('br/public:avm/res/db-for-postgre-sql/flexible-server:0.9.1') and when creating the database I have an error message during configuration step :
server is « is busy with another operation. Please try again later."
• Server 'psqltest00502' is busy with another operation. Please try again later.
(Code: ResourceDeploymentFailure, Target: /subscriptions/f5c25c0b-39d1-48b7-a644-c1f6b4d83b49/resourceGroups/rgcz2409lab01/providers/Microsoft.DBforPostgreSQL/flexibleServers/psqltest00502/configurations/pgaudit.log)
o -
Server 'psqltest00502' is busy with another operation. Please try again later. (Code: ServerBusy)
The text was updated successfully, but these errors were encountered: