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

workflow failure (unprovoked?): Failed to deploy the Azure Functions #638

Closed
sig9 opened this issue Nov 19, 2021 · 4 comments
Closed

workflow failure (unprovoked?): Failed to deploy the Azure Functions #638

sig9 opened this issue Nov 19, 2021 · 4 comments

Comments

@sig9
Copy link

sig9 commented Nov 19, 2021

Describe the bug

The Build and Deploy step of our githoub action is failing. Started yesterday when we opened a PR. Re-run all jobs continues to fail today.

This has been working reliably until now. The log messages are not helpful, not sure where else to look for clues. seems like an infrastructure/hosting/service issue from what we can see here. The PR doesn't have any changes to the api functions.

To Reproduce
Steps to reproduce the behavior:

  1. Open a PR
  2. Wait for failed Build and Deploy Job with message - Failed to deploy the Azure Functions
  3. re-run all jobs
  4. Wait for failed Build and Deploy Job with message - Failed to deploy the Azure Functions

image

screenshot of the workflow yaml
image

@riverar
Copy link

riverar commented Nov 19, 2021

Seeing same issue, hard to get any diagnostic information. @anthonychu

@kbarnes3
Copy link

I'm seeing the same issue on two separate projects that use Azure Functions. I have other projects that use Static Web Apps to deploy just an Angular frontend with no Azure Functions associated and these continue to work fine.

@miwebst
Copy link
Contributor

miwebst commented Nov 19, 2021

We are tracking this here. There is an issue with Azure Functions: #632

@miwebst miwebst closed this as completed Nov 19, 2021
@miwebst
Copy link
Contributor

miwebst commented Nov 19, 2021

Sorry wrong link, this is the correct one: #622

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants