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

Response status code does not indicate success: 503 (Service Unavailable) #11597

Closed
5 tasks
jkotas opened this issue Nov 11, 2022 · 6 comments
Closed
5 tasks
Assignees

Comments

@jkotas
Copy link
Member

jkotas commented Nov 11, 2022

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=80098

Build leg reported

Build / Installer Build and Test coreclr windows_x86 Debug / Build

Pull Request

dotnet/runtime#78208

Action required for the engineering services team

To triage this issue (First Responder / @dotnet/dnceng):

  • Open the failing build above and investigate
  • Add a comment explaining your findings

If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:

  1. Add the label "Known Build Error"
  2. Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation
{
   "ErrorMessage" : "error NU1301: Response status code does not indicate success: 503 (Service Unavailable)",
   "BuildRetry": true
}

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

Why is this not getting linked to a known infrastructure issue?

Report

Build Definition Step Name Console log Pull Request
80282 dotnet/sdk Build Log dotnet/sdk#29022
80098 dotnet/runtime Copy native test components to test output folder Log dotnet/runtime#78208
80074 dotnet/runtime Libraries Test Run checked coreclr windows arm64 Release Log
80064 dotnet/runtime Build Log dotnet/runtime#77884
80052 dotnet/runtime Build Log dotnet/runtime#77874
80019 dotnet/roslyn Build and Test Log dotnet/roslyn#64160
Build Definition Test Pull Request
80108 dotnet/sdk dotnet.Tests.dll.8.WorkItemExecution dotnet/sdk#29018

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 7
@oleksandr-didyk
Copy link
Contributor

Hey, taking a look at this, will let you know once we have any updates

@oleksandr-didyk
Copy link
Contributor

I re-ran the failed pipeline and the artifacts were retrieved successfully, so this seems to have been a one-of issue.

Please feel free to re-open it if you encounter the problem again

@jkotas
Copy link
Member Author

jkotas commented Nov 11, 2022

This is not a one-off issue. I have seen number of jobs failing in last few days with the nuget service unavailable errors. Here is a random example from a different job: https://dev.azure.com/dnceng-public/public/_build/results?buildId=79388&view=logs&j=af986455-df3a-5ed6-b067-9144b6c8d0c6&t=2f3069f0-e001-503f-08a5-20cd64bd1e2e&l=165

Do you have a telemetry for how many CI jobs are failing with these 50* errors?

@jkotas jkotas reopened this Nov 11, 2022
@oleksandr-didyk
Copy link
Contributor

Sure thing, will take a look

@MilenaHristova
Copy link
Member

We've had this problem with the Nuget feeds because of volume, we're working with the Nuget team to resolve it. You can see more in this issue: #10885

@ilyas1974
Copy link
Contributor

It appears that the Nuget feed issues that we put into place have resolved this issue as we have not seen any additional instances for 7 days. Should you see this issue again, please let us know.

@ilyas1974 ilyas1974 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants