New Deployment Failed - adminweb

[mirojs]

Describe the bug

A clear and concise description of what the bug is.

New deployment failed upon executing azd up. The adminweb was not there in the resource group.

Expected behavior

A clear and concise description of what you expected to happen.

How does this bug make you feel?

Share a gif from giphy to tells us how you'd feel

---

Debugging information

Steps to reproduce

Steps to reproduce the behavior:

1. Run azd up
2. See error:

Deploying services (azd deploy)

(x) Failed: Deploying service adminweb

ERROR: getting target resource: resource not found: unable to find a resource tagged with 'azd-service-name: adminweb'. Ensure the service resource is correctly tagged in your infrastructure configuration, and rerun provision

ERROR: error executing step command 'deploy --all': getting target resource: resource not found: unable to find a resource tagged with 'azd-service-name: adminweb'. Ensure the service resource is correctly tagged in your infrastructure configuration, and rerun provision

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

If applicable, add logs to help the engineer debug the problem.

---

Tasks

To be filled in by the engineer picking up the issue

• [ ] Task 1
• [ ] Task 2
• [ ] ...

[superhindupur]

Thanks for the bug report @mirojs. Can you check your .azure/your-env-name/.env file and tell me what the value of the AZURE_APP_SERVICE_HOSTING_MODEL variable is?

[mirojs]

@superhindupur Thanks for the super fast response! It's AZURE_APP_SERVICE_HOSTING_MODEL="container"

[superhindupur]

Ok, if you're deploying from your clone of the repo, please follow the instructions at https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/LOCAL_DEPLOYMENT.md.

Specifically, you need to run

azd env set AZURE_APP_SERVICE_HOSTING_MODEL code

before azd up.

[superhindupur]

@mirojs can you confirm whether that fixed your problem?

[mirojs]

@superhindupur For the previous deployed one, after using azd down -> azd up, it worked again. For brand new deployment, it would prompt "ERROR: listing accounts: listing subscriptions: failed to load subscriptions from tenant 'Default Directory' : reauthentication required, run azd auth login --scope https://management.azure.com//.default to log in; failed to load subscriptions from tenant '---' : reauthentication required, run azd auth login --scope https://management.azure.com//.default to log in". And the reauthentication didn't work.

[mirojs]

@superhindupur For the previous deployed one, after using azd down -> azd up, there's an error "ERROR - Container web-...-admin_... for site web-...-admin has exited, failing site start "

[mirojs]

@superhindupur Managed For brand new deployment, azd auth logout -> azd auth login -> azd up -> ERROR: error executing step command 'package --all': failed packaging service 'adminweb': failed invoking event handlers for 'prepackage', 'prepackage' hook failed with exit code: '127', Path: '/tmp/azd-prepackage-1333944515.sh'. : exit code: 127, stdout: , stderr: /tmp/azd-prepackage-1333944515.sh: 5: poetry: not found

[superhindupur]

Looks like you might not be running with a devcontainer. Are you following the steps at https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/LOCAL_DEPLOYMENT.md exactly?

[mirojs]

@superhindupur Yep, exactly

[mirojs]

@superhindupur Sorry, I git clone from the repo first and then followed step 4 to 6 in the link since I need a private repo for the following code update

[superhindupur]

Ok,. Are you using VSCode? You will need to install the DevContainers extension for VSCode and open the Chat With Your Data project inside a DevContainer (https://code.visualstudio.com/docs/devcontainers/containers#_quick-start-open-an-existing-folder-in-a-container). Then you can follow https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/LOCAL_DEPLOYMENT.md from step 4.

[mirojs]

@superhindupur I'm not using VSCode but I could give it a try if that a must. In the meanwhile, how should the public repo update be synced and merged smoothly in that case?

[superhindupur]

There's another option. If you aren't using VSCode (and therefore can't use the devcontainers extension), follow https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/main/docs/NON_DEVCONTAINER_SETUP.md

You can ignore the VSCode section, but install all the other mentioned tools. In your error message, you were missing 'poetry', which you will need to install (https://python-poetry.org/docs/)

[mirojs]

@superhindupur It's deploying! One poetry away, thanks a million!

BTW, for one previous deployed App (git clone -->azd up), which was broken (container apps shown in resource group) following the public repo update, I did azd down --purge --> azd env set AZURE_APP_SERVICE_HOSTINGMODEL code --> azd up last night and the deployment went through but adminweb app could not be started now with "ERROR - Container web-...-admin... for site web-...-admin has exited, failing site start".

Any clue why container was mentioned in the error message? Anything else I could do to clean up further without starting over everything from the very beginning? Thanks.

[mirojs]

@superhindupur After deploying for a 3rd time, it started to work by itself. Not sure why. And thanks for the help!

[ross-p-smith]

@mirojs - can I close this?

[mirojs]

@ross-p-smith please, thanks for the help!