M03-Implementing GitHub Actions for CI/CD : GitHub Actions can't find the Web app that already been provisioned.

Question

M03-Implementing GitHub Actions for CI/CD : GitHub Actions can't find the Web app that already been provisioned.

msftnutta opened this issue 8 months ago · 13 comments

msftnutta commented 8 months ago

Contact Details

No response

What happened?

Github actions triggered and often get the error as shown the screen shot.

App Service Plan, App Services, all correct but it failed at this pointed too often before succeeding it.

Lab

Other

Relevant screenshots

Do you want to help us? 👏

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

Answer 1 · 2024-03-20T16:22:26.000Z

These seems to be an intermittent issue that affects both GitHub webapp-deploy
Azure/webapps-deploy#227

and Azure DevOps
https://learn.microsoft.com/en-us/troubleshoot/azure/devops/resource-not-exist-error-services-deployment

We can consider putting a delay into the pipeline, but that will impact the all of the happy path students as well.

Answer 2 · 2024-03-21T13:14:16.000Z

Had the same thing this week. 10 - 15 minutes was the wait time before it appeared.

Answer 3 · 2024-04-02T20:42:27.000Z

Looks like the same issue that affects the Azure Pipeline task: microsoft/azure-pipelines-tasks#15532. Solution for me was to use the command-line, which isn't affected by this issue. https://github.com/maartenvandiemen/TodoItems/blob/main/.github/workflows/main.nodocker.yml (line 86, 87).

If people agree, I can make a PR to use the command-line instead of the out-of-the-box tasks.

Answer 4 · 2024-04-02T23:38:30.000Z

@maartenvandiemen go for it

Answer 5 · 2024-04-04T21:49:29.000Z

@yashints to start with I created PR: MicrosoftLearning/eShopOnWeb#140. In webapps-deploy@v3 the upgrade mechanism is changed, so maybe this will fix the issue already. If not please give feedback and I will do the change as suggested above.

Answer 6 · 2024-04-04T23:07:08.000Z

thanks, I will need to test these first

cc: @rob-foulkrod

Answer 7 · 2024-04-05T22:15:47.000Z

... to start with I created PR: MicrosoftLearning/eShopOnWeb#140. In webapps-deploy@v3 the upgrade mechanism is changed, so maybe this will fix the issue already. If not please give feedback and I will do the change as suggested above.

@maartenvandiemen, I think the upgrade is helpful, however, I have my doubts that this will have any impact of the issue at hand. Azure/webapps-deploy@v3 was released in October of last year, and issues are still being raised as of February of the current year. In addition, nothing in the list of difference between v2 and v3 mention dealing with the caching issue of the API call. If you have the bandwidth, I think we would love to take a look at a CLI based deploy.

Answer 8 · 2024-04-05T22:21:19.000Z

@rob-foulkrod thanks for the feedback. I will do the change next week and update the PR. For the other tasks I think it's good to keep them on the maximum major version.

Answer 9 · 2024-04-15T20:00:29.000Z

PR approved. Closing the issue for now, let me know if you still see it.

Answer 10 · 2024-04-15T20:29:49.000Z

@LuizMacedo @rob-foulkrod @yashints I didn't have time to update PR: MicrosoftLearning/eShopOnWeb#140 with the CLI approach. But it's stil on my list. (In my opinion it's better to have it in a separate PR). I will leave it up to you to reopen this issue or not.

Answer 11 · 2024-04-15T20:38:27.000Z

Thanks, @maartenvandiemen! I agree, a separate PR is good.

Answer 12 · 2024-04-18T22:07:36.000Z

@LuizMacedo @rob-foulkrod @yashints created CLI based deployment in above PR. I haven't heard anyone who experienced this issue after the upgrade of Github tasks.

Answer 13 · 2024-04-19T13:17:29.000Z

Thanks for the contribution @maartenvandiemen. I will take a look at it this weekend. And I agree, I have never had a problem pushing a site with the CLI tooling.