M04-LAB07 Controlling Deployments using Classic Release Gates - problem when deploying eshoponweb new code

[jajjaf]

Contact Details

No response

What happened?

Exercise 3: Configure the release pipeline Task 1: Set Up Release Tasks Step: Switch to the Azure portal interface, navigate to the resource group az400m04l09-RG, in the list of resources, click the DevTest web app, on the web app blade, click Browse, and verify that the web page (E-commerce website) loads successfully in a new web browser tab.

Description of issue: the code of the e-SohopOnWeb application has been updated and when we deploy in a web app there is always the following error, does anyone have this same problem, below is a screenshot, this blocks the rest of the lab and the other labs too since it is always the same code to deploy thanks Below is a screenshot.

Lab

Control Deployments using Release Gates

Relevant screenshots

Do you want to help us? 👏

• [ ] Create a Pull Request by following this project's Contribution Guide

[jajjaf]

@LuizMacedo since the last merge, deployment is no longer done correctly in Azure webapps, this is also valid for lab 16 thanks

[LuizMacedo]

Thanks @jajjaf. I'm on it and I'll fix as soon as possible.

[LuizMacedo]

It's fixed. Issue was the old bicep folder path in the .yml files from the .ado folder.

[jajjaf]

@LuizMacedo Thank you, even with the modified Bicep path there is an application problem, when it is pushed to a web app it still displays the same error message. THANKS

[LuizMacedo]

Interesting. I'll reopen the issue so I can dig deeper. We will probably need to update the lab and publish in an App Service to resolve it.

[jajjaf]

@LuizMacedo it may be a configuration problem or migration to version 8 of dotnet, and it's the same thing for a few other Labs. Thanks

[jajjaf]

@LuizMacedo @yashints Thank you for your quick interaction I tested with the new version of the code that you recently merged, the eshoponweb application once deployed in the web still displays the same error message the rest of the labs are blocked

[LuizMacedo]

@jajjaf @yashints I'll reopen the issue to double check. It worked for me yesterday. So, after successful deployment you still see the HTTP 500?

[jajjaf]

@LuizMacedo @yashints yes absolutely I redeployed with the latest version still the same error

[sofiing1985]

Hello I test the lab 16 today and I can confirm that I have the same issue mentioned by @jajjaf

[LuizMacedo]

Thanks @jajjaf @sofiing1985 I'll try to check it today. The last update from @yashints should have resolved the issue. I'll check what else is missing.

[rob-foulkrod]

Currently, I cannot reproduce the error when I have the latest Eshop and the latest instruction set.

Make sure you are seeing Exercise 3 Task 1 Step 14 "Open the Application and Configuration Settings pane and enter -UseOnlyInMemoryDatabase true -ASPNETCORE_ENVIRONMENT Development in the App settings box."

If you open the Environment Variables pane you should see the following:

You can often fix a mis-deployed site by adding

• UseOnlyInMemoryDatabase: true
• ASPNETCORE_ENVIRONMENT: Development

[LuizMacedo]

@jajjaf @sofiing1985 please, let us know if it works following @rob-foulkrod suggestion. Thanks!

[jajjaf]

Indeed with these two variables it works very well thanks @LuizMacedo @rob-foulkrod @sofiing1985