We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If you submit an Azure Batch pipeline which tries to create a pool when the pool already exists, you get the following error:
Caused by: Status code 409, "{ "odata.metadata":"https://mybatch.eastus.batch.azure.com/$metadata#Microsoft.Azure.Batch.Protocol.Entities.Container.errors/@Element","code":"PoolExists","message":{ "lang":"en-US","value":"The specified pool already exists.\nRequestId:d9475bc1-f9e5-492b-9114-6a05a8a57abc\nTime:2025-01-23T14:15:51.6526349Z" } }"
We can just ignore this error since the pool is being created.
Related to #5575
We can add the code here:
nextflow/plugins/nf-azure/src/main/nextflow/cloud/azure/batch/AzBatchService.groovy
Line 926 in 19c40a4
or an explicit exception here:
Lines 935 to 947 in 19c40a4
The text was updated successfully, but these errors were encountered:
feat(azure-batch): Ignore pool already exists error
3b14485
Ignores pool already exists error and continues. Fixes nextflow-io#5713 Signed-off-by: adamrtalbot <12817534+adamrtalbot@users.noreply.github.com>
Successfully merging a pull request may close this issue.
New feature
If you submit an Azure Batch pipeline which tries to create a pool when the pool already exists, you get the following error:
We can just ignore this error since the pool is being created.
Usage scenario
Related to #5575
Suggest implementation
We can add the code here:
nextflow/plugins/nf-azure/src/main/nextflow/cloud/azure/batch/AzBatchService.groovy
Line 926 in 19c40a4
or an explicit exception here:
nextflow/plugins/nf-azure/src/main/nextflow/cloud/azure/batch/AzBatchService.groovy
Lines 935 to 947 in 19c40a4
The text was updated successfully, but these errors were encountered: