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.

Sign up for GitHub

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

Jump to bottom

az containerapp up fails after creating 25 workspaces #6256

Closed
pamelafox opened this issue May 2, 2023 · 5 comments
Closed

az containerapp up fails after creating 25 workspaces #6256

pamelafox opened this issue May 2, 2023 · 5 comments
Labels
Auto-Assign Auto assign by bot ContainerApp CXP Attention This issue is handled by CXP team. 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

@pamelafox
Copy link
Member

This is autogenerated. Please review and update as needed.

Describe the bug

Instead of creating the typical set of resources, az containerapp up generated 1 ACA environment, 25 log analytic workspaces and then gave up.

Command Name
az containerapp up Extension Name: containerapp. Version: 0.3.28.

Errors:

@pamelafox ➜ /workspaces/simple-flask-server-container-starter (main) $ az containerapp up --resource-group flaskapp-rg --name flaskapp-aca \
    --ingress external --target-port 50505 --source .

Using resource group 'flaskapp-rg'
Creating ContainerAppEnvironment 'flaskapp-aca-env' in resource group flaskapp-rg
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgKvkh"

/ Running ..
| Running ..
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgNueN"


No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgsa2k"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgSepL"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg2Lgy"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgbNs2"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg4PPo"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg3KMe"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgNoP5"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgpCen"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgHJci"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgCDZl"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg2I7Y"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgSqxf"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgj1qg"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg1rBb"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprggVIt"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgC7W5"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgsuvO"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgdVTr"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgkv4u"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgJVMy"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgQgMV"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgiIQ4"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgFcOq"
Can not find a region with quota to create ManagedEnvironment

To Reproduce:

I don't know whether it will reproduce, but I would suggest trying it on this repository/branch:

https://github.com/pamelafox/simple-flask-server-container-starter/tree/reproduce

Open that in Codespaces.

Then, after creating a resource group, run:

az containerapp up --resource-group flaskapp-rg --name flaskapp-aca \
    --ingress external --target-port 50505 --source .

Expected Behavior

I expect it to create a single Log Analytics workspace, single Container App, single Container App Environment, single Container Registry. Instead, it only made a Container Apps Environment and 25 Log Analytic workspaces.

Environment Summary

GitHub Codespaces

Linux-5.4.0-1106-azure-x86_64-with-glibc2.31, Debian GNU/Linux 11 (bullseye)
Python 3.10.10
Installer: DEB

azure-cli 2.48.1

Extensions:
containerapp 0.3.28

Dependencies:
msal 1.20.0
azure-mgmt-resource 22.0.0

Additional Context

Please let me know if you need any information from the resource group, otherwise I'd like to delete it to avoid accruing costs. Thanks!
@ghost ghost added Auto-Assign Auto assign by bot ContainerApp labels May 2, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented May 2, 2023

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

@ghost ghost added the CXP Attention This issue is handled by CXP team. label May 2, 2023
@SwathiDhanwada-MSFT SwathiDhanwada-MSFT self-assigned this May 3, 2023
@SwathiDhanwada-MSFT SwathiDhanwada-MSFT added the question The issue doesn't require a change to the product in order to be resolved. Most issues start as that label May 3, 2023
@SwathiDhanwada-MSFT
Copy link

@pamelafox Thanks for your comment. We will review the issue and get back to you shortly.

@SwathiDhanwada-MSFT SwathiDhanwada-MSFT added the Service Attention This issue is responsible by Azure service team. label May 11, 2023
@SwathiDhanwada-MSFT SwathiDhanwada-MSFT removed their assignment May 11, 2023
@ghost
Copy link

ghost commented May 11, 2023

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @calvinsID.

Issue Details

This is autogenerated. Please review and update as needed.

Describe the bug

Instead of creating the typical set of resources, az containerapp up generated 1 ACA environment, 25 log analytic workspaces and then gave up.

Command Name
az containerapp up Extension Name: containerapp. Version: 0.3.28.

Errors:

@pamelafox ➜ /workspaces/simple-flask-server-container-starter (main) $ az containerapp up --resource-group flaskapp-rg --name flaskapp-aca \
    --ingress external --target-port 50505 --source .

Using resource group 'flaskapp-rg'
Creating ContainerAppEnvironment 'flaskapp-aca-env' in resource group flaskapp-rg
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgKvkh"

/ Running ..
| Running ..
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgNueN"


No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgsa2k"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgSepL"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg2Lgy"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgbNs2"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg4PPo"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg3KMe"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgNoP5"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgpCen"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgHJci"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgCDZl"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg2I7Y"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgSqxf"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgj1qg"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprg1rBb"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprggVIt"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgC7W5"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgsuvO"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgdVTr"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgkv4u"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgJVMy"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgQgMV"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgiIQ4"
No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-flaskapprgFcOq"
Can not find a region with quota to create ManagedEnvironment

To Reproduce:

I don't know whether it will reproduce, but I would suggest trying it on this repository/branch:

https://github.com/pamelafox/simple-flask-server-container-starter/tree/reproduce

Open that in Codespaces.

Then, after creating a resource group, run:

az containerapp up --resource-group flaskapp-rg --name flaskapp-aca \
    --ingress external --target-port 50505 --source .

Expected Behavior

I expect it to create a single Log Analytics workspace, single Container App, single Container App Environment, single Container Registry. Instead, it only made a Container Apps Environment and 25 Log Analytic workspaces.

Environment Summary

GitHub Codespaces

Linux-5.4.0-1106-azure-x86_64-with-glibc2.31, Debian GNU/Linux 11 (bullseye)
Python 3.10.10
Installer: DEB

azure-cli 2.48.1

Extensions:
containerapp 0.3.28

Dependencies:
msal 1.20.0
azure-mgmt-resource 22.0.0

Additional Context

Please let me know if you need any information from the resource group, otherwise I'd like to delete it to avoid accruing costs. Thanks!

Author: pamelafox
Assignees: SwathiDhanwada-MSFT
Labels:

question, Service Attention, CXP Attention, Auto-Assign, ContainerApp
Milestone: -

@SwathiDhanwada-MSFT
Copy link

As this issue is not customer reported, redirecting it to Service Team.

@pamelafox Kindly include debug output in the issue. You can get the debug output by adding --debug parameter.

az containerapp up --resource-group flaskapp-rg --name flaskapp-aca \
    --ingress external --target-port 50505 --source . --debug

@pamelafox
Copy link
Member Author

I added --debug but the issue is no longer happening. I'll close this and re-open with --debug output if I see it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Auto-Assign Auto assign by bot ContainerApp CXP Attention This issue is handled by CXP team. 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pamelafox @SwathiDhanwada-MSFT @yonzhan