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

Container Apps are always created in the wrong region (az containerapp compose create) #7542

Open
vienleidl opened this issue Apr 23, 2024 · 2 comments
Labels
Auto-Assign Auto assign by bot ContainerApp customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@vienleidl
Copy link

Describe the bug

Even though, the location is stated in the az containerapp compose create command with southeastasia, but the Container Apps Environment and its Container Apps are always created in the WEST US 2 region as unexpectedly.

Related command

az containerapp compose create -g ResourceGroupName --environment ContainerAppEnvName --location southeastasia

OR

az containerapp compose create -g ResourceGroupName --environment ContainerAppEnvName -l southeastasia

OR

az containerapp compose create -g ResourceGroupName --environment ContainerAppEnvName --location "Southeast Asia"

Errors

The Container Apps Environment and its Container Apps are always created in the wrong region on Azure portal.

Issue script & Debug output

cli.knack.cli: Command arguments: ['containerapp', 'compose', 'create', '-g', 'ResourceGroupName', '--environment', 'ContainerAppEnvName', '--location', 'Southeast Asia', '--compose-file-path', './docker-compose.yml', '--registry-server', 'acr.azurecr.io', '--registry-username', 'acr-username', '--registry-password', 'acr-pass', '--debug']
az_command_data_logger: extension name: containerapp
az_command_data_logger: extension version: 0.3.50
cli.azure.cli.core.commands: The behavior of this command has been altered by the following extension: containerapp
cli.azure.cli.core.sdk.policies: Request method: 'GET'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies: 'Accept': 'application/json'
cli.azure.cli.core.sdk.policies: 'CommandName': 'containerapp compose create'
cli.azure.cli.core.sdk.policies: 'ParameterSetName': '-g --environment --location --compose-file-path --registry-server --registry-username --registry-password --debug'
cli.azure.cli.core.sdk.policies: 'User-Agent': 'AZURECLI/2.59.0 (MSI) azsdk-python-core/1.28.0 Python/3.11.8 (Windows-10-10.0.22631-SP0)'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: This request has no body
cli.azure.cli.core.util: {"error":{"code":"ResourceNotFound","message":"The Resource 'Microsoft.App/managedEnvironments/ContainerAppEnvName' under resource group 'ResourceGroupName' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"}}
cli.azext_containerapp.custom: Creating the Container Apps managed environment ContainerAppEnvName under ResourceGroupName in southeastasia.

Expected behavior

The Container Apps Environment and its Container Apps should be created in the Southeast Asia region as stated in the az containerapp compose create command.

Environment Summary

azure-cli 2.59.0
core 2.59.0
telemetry 1.1.0

Extensions:
aks-preview 3.0.0b5
azure-devops 1.0.0
containerapp 0.3.50

Dependencies:
msal 1.27.0
azure-mgmt-resource 23.1.0b2

Additional context

The same issue happens also in Azure DevOps release pipelines.

@vienleidl vienleidl added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Apr 23, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Apr 23, 2024

Thank you for opening this issue, we will look into it.

@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. Auto-Assign Auto assign by bot ContainerApp Service Attention This issue is responsible by Azure service team. labels Apr 23, 2024
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Apr 23, 2024
@Greedygre
Copy link
Contributor

Hi @vienleidl

Thanks for reporting this issue.
I checked and there is a bug when creating a new environment during az containerapp compose it doesn't use the input location. I will fix it.

For workaround:
Create a environment in southeastasia first:
az containerapp env create -g ResourceGroupName --environment ContainerAppEnvName --location southeastasia
Then execute the compose command.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot ContainerApp customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants